Are you seeing a case now where someone can't edit the description depending on the state?
Check if your workflow uses the workflow property jira.issue.editable in the transition leading to the state you can no longer edit in. That property is what makes the issue uneditable.
If you remove that, then anyone can edit the issue in that state again.
If you however want to limit who can edit it depending on state, then yes you will need Behaviors or Live Fields
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Vanessa,
Any project role can be granted the ability to edit issues. Are you asking if there is a way that the role could edit just that one field? If so, I think that is where Hernan was going with the Behaviors suggestion.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I would consider start using behaviors for this
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.