I wanted to add "Epic Link" to our custom screens, so in order to do that I first unlocked the Epic Link as per the documentation (https://confluence.atlassian.com/display/AGILEKB/How+to+unlock+a+Locked+field) , added it to the screen I also set it to "Required" as we wanted it mandatory in screens ( using the field configurations). Locked the field again. But whenever our JIRA server restarts the field is no more "Required" in the screens. Any idea why its happening ?
Thanks in advance for the help.
We're experiencing the same issue. Any solutions to making this setting persistent through a JIRA restart yet?
We too needed to do the unlock/lock thing, as making this mandatory in workflows doesn't cover the 'move' case (e.g. if you make Epic Link a required field for Stories, on the Create transition, people can still 'move' a bug or Task to a Story, and avoid this requirement because the issue is already created.
Thus we need to have it set as 'required'.
Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs