Expand my Community achievements bar.

Join us LIVE in San Francisco on November 14th for Experience Makers The Skill Exchange. Don't miss out on this free learning event!

Condition Titles

Avatar

Level 4

4/5/17

Please change the names of the conditions. At Risk and In Trouble really can cause a lot of concern and would like to see some names change such as "At Risk" to something less concerning such as Review needed, etc.

10 Comments

Avatar

Level 5

4/5/17

Would be great if we could customize the names of the conditions to equate to the applicable Workfront system value. This feature is currently available to us on project, task and issue statuses (Setup > Project Preferences > Statuses) shown in the screen illustration below.

Avatar

Level 10

6/4/17

Absolutely....we really want to be able to customise the Condition labels at Task and Project levels, as "In Trouble" is sometimes a bit too strong a term, however we still want to set Condition based on Progress Status, not manually. I propose a couple of other enhancements:

  1. Allow a sensitivity setting for Condition Type based on progress status. Often our resource are up to 1 day late in marking their tasks complete. Rather than having projects immediately show as At Risk or Late (which concerns PMs and management unnecessarily in most cases) it would be best if the project could allow a configurable sensitivity buffer of e.g. 1 day. If they are more than 1 day late updating the task then the project would move to Late etc.
  2. Add some logic for setting Condition Type based on progress status and take into account whether the project is still in progress or not. If a project is Complete or Dead, it shouldn't retain a condition status of 'In Trouble'. This would suggest that it is not final, however the project status is final. Really, the final Condition should change to "Late" to indicate that the project was completed late.

Regards, David

Avatar

Level 3

6/22/18

Absolutely. Every single queue which is active is also "in trouble," which is nonsense. Being able to disable this for queues and other projects would be helpful.

Avatar

Level 10

12/4/18

Agreed. We use a custom project-level field called "Overall RAG" - which also obviously has 3 options, so being able to just rename the Condition values would be an immediate win.

Avatar

Level 3

4/11/19

Good news, we are taking this one on! We will be starting shortly and our plan is to have something available in preview in the next couple of months. I'll come back and update as we get closer to that date and have a more firm timeline.

Avatar

Level 1

6/14/19

Hi, just following up here again. We are tracking to have the Custom Conditions enhancement available on the Preview environment in the next 2-3 weeks. Production will follow sometime after that. I will be sure to post back here when we are ready for a release to Preview.


Josh Hardman

Product Manager, Workfront

Avatar

Level 3

7/3/19

I am excited to announce that this enhancement will be available on Preview with the 2019.3 Beta 4 Preview release that is scheduled for July 4th, 2019! We have still not yet set a production date.


You can find a short demo video of this capability along with links to documentation here:

https://experience.workfront.com/s/article/2019-3-Release-Activity-Overview-1993224231

Avatar

Level 1

10/31/19

I am happy to report that this has been released to production! You should be able to create custom conditions as well as change the labels for the built in conditions from access Setup -> Project Preferences -> Conditions.


Josh Hardman

Product Manager, Workfront