Adding another choice for STATUS on Project task form

[PaulaaO]

Hi Community,

I have the following requirement from my portfolio stakeholders: add another choice in the status field from Project Task form called Complete and to appear against Blue colour when reviewed on Planning Console (Classic or New Project Workspace) or in the Project Task list of records.

I wanted to ask first whether this is something we should customise at all or leave alone.

If we can proceed and customise this, what is the best approach and what are the relevant components that need updating/creating for this to work, without impacting the current behaviour of the field, given that as per the documentation "it updates automatically based on the difference of the planned end date of the task from the current date".?

The status would change to this new choice whenever the State would become one of the Closed values (Closed Complete, Closed Incomplete, Closed Skipped).

I assume I will need to create a Business Rule for this as well, however my main concern is how to address this whilst maintaining most of the current behaviour of this field.

Any suggestions would be highly appreciated.

Thank you.

Paula

[Neel Patel]

If I understood it correctly, you just need to add a new state option. And for Colors you can use the create a style based on condition. This would be configuration instead of customization.

[PaulaaO]

Hi @Neel Patel , I need to add a new status option, but which will be triggered when the state will be one of the closed ones. My concern is around the calculation of status field as I don't want to impact the OOTB behaviour when the project task is in any active states (Pending, Open, WIP).

Would you mind sharing the link or the table name for the style bit please? I found this list on styles: 

sys_ui_style, but this only enables the colour on project task list of records, don't know how to do it in the Classic and New Project Workspace.

Thank you 🙂

[Community Alums]

Hello Neel,

This was really helpful.

I'm an IT PM and we are currently working on improving our demand process. Some of my stakeholders are requesting the creation of new forms or similar changes to the planning console, as described by PaulaaO. I've been told that making modifications to forms or the workspace is considered customization, and in my situation, it involves creating user stories and going through a pretty lengthy process in order to implement the customization.

Is there a documentation available to help me, as the project manager, in understanding the difference between configuration and customization. The modification to our workspace was requested by my stakeholders, as mentioned by PaulaaO, was brought up in the past but was ultimately tabled because we were told that it was considered a customization. Any impute would be greatly appreciated. 

[PaulaaO]

Hi @Community Alums - my only advice is be very very careful with customisation and modifying out of the box behaviours. Ensure the behaviour is fully understood by the Product Owner and by the stakeholders before going on this route - only mentioning this because last few years one of my main focuses was to revert customisations at project level which has been a pain. Plus you need to remember that any customisation means that enhancements brought by upgrades will be skipped. Unless you create a list of all customisations done and this is being reviewed ahead of upgrade in conjunction with release notes to be aware of the impact.