Why every field can get the helper text that shows their description but the status not? Why is there even a description of it? Do I really need to make a custom field, and automation for every time the issue transitions and with all the different descriptions added manually?
It sounds too crazy, it can't be that you cannot choose to display the description of the status as sort of a helper text in the huge and empty bar on your right...
Hello @Julian Varela Taja
Welcome to the Atlassian community.
This was acknowledged as a Bug by Atlassian but was closed in 2020 as Won't Fix.
https://jira.atlassian.com/browse/JRACLOUD-72871
You could open a support case directly with Atlassian asking their support team to open a new bug for this to see if traction can be gained on it now, 5 years later.
Wow, thanks! Let's see how it goes :)
It's crazy that a native field can't be just displayed. Specially when it can save so much work and help new users to find their way around a new tool...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Varela - Welcome to the Atlassian Community!
What is it that you are tying to accomplish? Are your status names so complicated that people wouldn't know what they mean? Also, you might can accomplish what you want just naming the transitions to be a little more descriptive.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi John, I should have been more descriptive, sorry. The statuses and transitions are named in a clear, logic and streamlined way. This is literally more the fact that there's a description field that's useless, in my case I wanted to display it as it describes what the validators and conditions are/do/need from the user.
For example, in order to perform a transition you need to have invited users to sign, this is the natural In Progress to a Ready to Sign. So it's literally a helper text in the, mostly useless, right bar completely white in the screen :) The field description exists and it's there for a reason, it just cannot be displayed and for me that makes no sense. Creating extra fields and automations to display a native field is completely nonsense.
Thanks for the good feedback, best practice reminder and the reminder to always check the basics before anything else, I do read a lot in the community and your comment is something a lot of people might be struggling with, but just not in this case.
Keep it up, cheers!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.