e.g. Req_and_Def_Validate_Screen is used in Request/Defect's validate step, but it's not part of Request/Defect screen scheme. I thought a screen scheme will include all screens being used in that issue type.
JIRA doesn't have the full capability to explain the depth of disparate configurations - it's a *lot* of work to explain it. The idea that "something can see all screens in use" quickly gets very difficult - you've got multiple projects and issue types to deal with, which can all have different screens, schemes and workflows. It's a lot of code, when a better idea is to have admins learn it. It's also possible to leave screens hanging without schemes or use in workflows (usually by deleting the scheme or workflow where they were used). This is harmless, but it's neat to delete them when you're sure you don't need them.
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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