Hi
We are trying to use next-gen projects and have a couple of questions.
1. Is it possible to make a context field mandatory (doesn't seem to be). We need to ensure that some fields are always filled in on new issues
2. If a context field had (say) 6 possible values today and then next week I didn't want anyone to use one of the values and deleted it, would it be deleted from any existing issues which had that value or would it only not be available for new issues. We wanted a way to have a fluid list of possible values dependent on where we are in the project but don't want to lose historical information.
Thanks
Karen
Hi Karen, a solution for #1 could the use of transition 'Rules' in the workflow.
For example, I ask users to provide a reason when they transition a ticket to the ON-HOLD status.
Not sure on #2, should be easy to test though.
At the American Academy of Family Physicians, siloed marketing teams faced delays and duplicate work. Kerrie Gottschalk shook things up by moving the department to Jira, streamlining processes, boosting visibility, and sparking stronger collaboration.
Read the story
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.