Skip to main content

Ideas

Filter by idea status

10000+ Ideas

BethBa4Level 2

Converting an Issue/Request to a Project be able to change the start date and durationNew

Description -It would be beneficial when converting an issue/request from a request queue to be able to adjust the start date right away along with the duration. Why is this feature important to you - Our maintenance queue takes in 200-300 requests per month and one project manager (me) is assigned to make sure that work moves along in a timely manner.  The resource pool contains 10-15 people to draw from so we can't assign the request out.    The start date is tied to the start date of the project which will always need to be manually edited unless it happens to come in on the first day of the project. How would you like the feature to work - When converting the request queue item to a task, bringing up the date range boxes as fillable would be beneficial.  At the end of our project period, the potential to make an error assigning to the wrong month is higher because the date defaults to the start of the active project.  The only way I've figured out how to edit is to go back into the project and edit those fields in the Task list.  It doesn't make sense the date would default to the start of the project because unless it is the same day, it will always be past. Current Behaviour -  We created a quarterly Maintenance Project to keep track of all the maintenance items for our web properties each month.  Many are one hit, simple tasks that take a resource 15 min-30 min to complete.  To spin every one of these into projects would take longer to set up the new project than it would to complete the task and would create hundreds of 1-2 line projects every month.  I have been converting the requests to tasks within a Quarterly project (Maintenance Queue 6/1-9/30 for example) to manage the duration/planned hours, resourcing capacity for this type of work, be able to make notes on the items and have the resource pool know these items can work with me as the PM if they run into scope creep or issues with the stakeholder.  It doesn't seem like I am able to assign the issue/request to someone without losing visibility to overall status of all the requests  After I convert to task within the project, I do not have the option to update the dates until I save.  At that time, I go back into the project, find the task I just converted and make the necessary adjustments.  I have all of the information when I convert the task so it would be nice to input it then instead of the extra steps to get it into the project first.

Add Association Between Custom Form Sections (parameterGroup) to Custom Form Values (parameterValues)New

I would like to be able to retrieve the custom form values (parameterValues), given a custom form section (categoryParameter) name or ID.  Currently, the API allows for Custom Form Names to be retrieved from a given Custom Form using the following api call:/proj/[projectID]/search?fields=objectCategories:category:categoryParameters:parameterGroup There is also an, unsupported, api call that allows for a "data dump" of all values in a given custom form, using the following api call:/proj/[projectID]/search?fields=*,parameterValues I would think that the "parameterValues" object would need to be added to the "parameterGroup" object.{ "data": { "ID": "", "name": "", "objCode": "PROJ", "objectCategories": [ { "ID": "", "objCode": "OBJCAT", "category": { "ID": "", "name": "", "objCode": "CTGY", "categoryParameters": [ { "objCode": "CTGYPA", "parameterGroup": { "ID": "", "name": "", "objCode": "PGRP", "parameterValues":{ "[customFormName]":"[value]" } } } } } ] } }If that isn't possible, maybe a simple GET call to get the "parameterValues" by a "parameterGroup" Name or ID.   This is important to our business because we use custom forms to integrate many systems. At times, these custom forms are very large and have many sections within them. We would like the ability to separate logic base on values from a given section with a custom form in order to keep scenario blueprints to a manage, maintainable size. Currently we are unable to separate logic in a scenario, based on custom form sections, within large custom forms bases on values from a given section with a custom form.

MikeySi
MikeySiLevel 2

Update time off language or designNew

DescriptionThe personal time off feature on Workfront is confusing from a design aspect and continually causes problems with teams trying to mark time off if they have a partial day off. The time off section says [Name] will be gone:✔ All dayFrom __ __To __ __ If you uncheck all day, then the system asks for your working hours. This is where it gets confusing to users because it still looks like the system is asking for your time off since it shows like this: [Name] will be gone: □ All dayWorking Hours:From __ __To __ __ The "working hours" is in a lighter grey color and appears small, so your eye is drawn to the [Name] will be gone, so it looks like that person should fill out the time they are gone, not the time they are available and working. Why is this feature important to youThis feature is important because even after training folks and bringing this to their attention, it still continues to cause confusion. This makes it challenging to know how accurate our calendar is when it continues to cause confusion. How would you like the feature to workIf the associates were able to indicate what time they are gone or unavailable to align better with the design.—OR—If the design could change to emphasize the "working hours" portion of the text box and not the "[Name] will be gone" portion to make it clear to people that they are stating what their availability is for that specific day. Current BehaviourCurrently the design is confusing. It first asks when you are gone, and if not the whole day, the question reverses itself to ask when you are available.