The Priority field is not present on the Field Screen for the Issue Type I created. However, It does appear in the Field Configuration. I am trying to find a way to let it appear for existing issues, but not be added when I create new issues, because eventually we want to turn off the Priority field.
I have applied a new Issue Type scheme, Workflow, Screen Scheme, and Field Scheme to an existing project that was already using the Priority field, so I can't Hide it in the Field Scheme or existing data will not be available.
Is there a solution?
Short answer: No, you can't have a subset of issues from the same issue type have a different screen and field configurations.
Workaround: You could create another issue type to use with these "old" issues. Give it any name makes sense to you. With this issue type, use a Screen Scheme and Field Configuration that has Priority. To prevent users from creating new issues using that old issue type, make it use a custom workflow where the Validator for creating issues can't be met by regular users, like having Administer Projects permission.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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