Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Request to Restore Editable Status Description Field in JPD

Jack Arndt September 20, 2023

Dear Atlassian Team,

Our organization noticed that the status description field is now locked as a system field. 

Previously we used the description section of the status field to document important process policies and information for our teams. Having this documentation visible within the tool itself was incredibly helpful to help promote transparency amongst our team on policies. 

With the status field now locked, that important information was erased during the update. I'm writing to politely request that you consider reverting the status field to be editable again in a future release. Having an editable status description field  is crucial for our teams to have the process information they need at their fingertips within JPD. Otherwise we have to send them to a confluence reference doc which is a much worse experience.

Please let me know if there is any additional context I can provide or if there are other solutions we could consider to restore this functionality. I appreciate you taking the time to review this request. Thank you in advance for your help!

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
2 votes
Answer accepted
Tanguy Crusson
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 25, 2023

Hi @Jack Arndt , Thanks for bringing this to our attention. It sounds like we put the cart before the wheel here, and released a change before we communicated it properly. It's been reverted and your status description should be back now.

However, this will only work like that in the short term (another 2 weeks), to give you time to copy the data somewhere else. After that it's going to be back to what you saw today. Here is more context:

I understand this is not the response you were after, but supporting this feature for Jira built-in fields would have introduced a lot of complexity - and we couldn't justify doing it based on its low usage. 

AUG Leaders

Atlassian Community Events