Why some screens are not part of any scheme?

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.


1 answer

Aside from the Screen scheme you can also use screens on Workflow transitions as you are aware of.

The screen scheme purpose is to make some default screens to be associated with Issue operations.

I hope it helps to clarify.



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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,187 views 5 10
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you