Issue Type Screen Scheme

Sorry for what might seem a very simple question but I'm new to Jira. I am struggling to get my head around the purpose of  Issue Type Screen Scheme. I get the need to set up a screen with fields, I get that you want assign these to Operations.. but then I get lost on the last bit.


I have read some Atlassian articles but its not helping.  Anybody able to give me some help? 

3 answers

1 accepted

0 votes
Mahesh S Community Champion Jun 08, 2016

Welcome to Jira! smile 

JIRA provides the platform for adding different screens for 'Create' 'Edit' and 'View' operation separately. For example, you have two Issue types 'issueA' and 'IssueB'. You may need different screens with respect to the issue types. So you can create 6 screens (like 'issueACreate', 'issueAEdit','issueAView' and similarly 3 for issueB) or you can utilize the same screens for all issue types as generic.

Then, in the next level you have to create Screen scheme. Here, you have to create two Screen Schemes - 'issueAScreenScheme' and 'issueBScreenScheme'. For example, 'issueAScreenScheme' will hold 'issueACreate', 'issueAEdit' and 'issueAView'.  This is to pack the screens specific to Issue types.

Finally. you have to create one Issue type screen scheme for a project. Here, you need to hold two Screen Schemes into this and map it with the issue type. For example, ProjectABScreenScheme can be associated to 'issueAScreenScheme' and 'issueBScreenScheme'. Where, 'issueAScreenScheme' can be mapped to 'issueA'.

I can also help you in the design if you share your architecture with fake values. Kindly let me know if you need any clarifications.

An issue type screen scheme connect an issue type to projects. Different projects can have different issue types. For example Project A might have stories and bugs, while project B might only have Tasks. 


When you create a scheme, you can them associate it to whatever projects you want. 



Issue Type Screen Schemes create the link between the issue types, the screens, and your project. 

Suppose you have a bug issue type on Project A, and bug issue type on Project B. In theory you can have different screens for bugs on each project.


Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,853 views 12 18
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot