How to set multiple issue type screen schemes for a single project

Henrik Gehrmann December 30, 2013

How can I have 1 project with different issue types that each show a different set of fields when that particular issue type is created?

I'd like to associate more than one screen scheme with a project.

Going to Projects > Screens > Actions. It looks like only 1 scheme can be selected.

See also https://confluence.atlassian.com/display/AOD/Associating+Screen+and+Issue+Operation+Mappings+with+an+Issue+Type

6 answers

2 accepted

9 votes
Answer accepted
Daniel Davkovski April 24, 2020

It's been few years since the comments here. 
This is what I have done to accomplish the need: 

 

1. Create new ISSUE TYPE:
a) Name --> this is the name that appears as issueType
b) Description --> optional
c) Standard Issue Type (unless you want it to be sub-task)

2. Create new SCREEN:
a) Name --> The name of the screen (for easy referencing use the same as IssueType you just created)
b) Description --> Provide more information about the screen that will help us easily adjust when/if needed
c) In the Field Tab add all the fields you want the issue to have (e.g. Summary, Description, Assignee etc...)

3. Create new SCREEN SCHEME:
a) Name --> The name of the screen scheme (for easy referencing use the same as IssueType you just created)
b) Description --> Provide more information about the screen scheme that will help us easily adjust when/if needed
c) Default Screen --> Select the previously configured SCREEN (from step 2)

4. Navigate to Issue Type Screen Scheme:
a) Locate the issue type screen scheme that is applied for the project which you are configuring
b) Under Action --> Configure
c) Associate an issue type with a screme scheme:
i) Issue Type --> Select the IssueType which you are configuring
ii) Screen Scheme --> Select the screen scheme you previously created for the screen and based on the issueType

5. Navigate to Issue Type Schemes:
a) Add Issue Type Scheme
i) Scheme Name --> Name it after the project for which you are creating
ii) Description --> Provide more information about the issue type scheme that will help us easily adjust when/if needed
iii) Default Issue Type --> leave at None
iv) Drag & Drop all the issue Types you want to have under this scheme (the ones created in step 1)
b) Locate the Issue Type Scheme you just created --> and Associate it with the project where you want it to apply

 

Note: This scenario is if you want completely customized issue Types, different fields based on the issueType, and all to apply within one same project. 

Shane_O_Sullivan May 18, 2020

This is a brilliant guide - thanks heaps

Like Daniel Davkovski likes this
Swati Rastogi October 15, 2020

Thanks a lot!! This was so helpful!

Like Daniel Davkovski likes this
S October 29, 2020

Brilliant - Should be part of JSD documentation:)

Like Daniel Davkovski likes this
Giorgio Crosali February 23, 2021

You saved my day, thanks @Daniel Davkovski 

Like Daniel Davkovski likes this
Daniel Davkovski February 23, 2021

Glad I can be of help everyone, and happy I was able to assist in some format on this. I know I was struggling to understand how to organize our Jira - so just my findings on a small piece of paper hopeful it'll help to others as well :D 

Like Shobana Kumar likes this
Bradley Pierskalla March 2, 2021

I can usually keep things straight and avoid getting wrapped around the scheme axles, but occasionally I still manage to mess something up. This just saved my sanity!

Like Daniel Davkovski likes this
Larkin Rogers April 18, 2021

You rock Daniel, you got me 90% of the way and then Nic's comment below completed it.  You are awesome, keep it up

Like # people like this
5 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 30, 2013

You are right that only one "Issue type screen scheme" can be associated with a project, but that is easy to confuse with a "Screen scheme". The "issue type screen scheme" is a collection of "screen schemes" - it says "in this project, use screen scheme 1 for issue types A, B and C, screen scheme 2 for D and E, and screen scheme 3 for any others".

So it does do what you need (and the other answers have the links you need)

Boyan Iliev February 21, 2020

Thank you! Sounds simple once you get it...

2 votes
LynF April 9, 2014

Thanks so much. This was as clear as mud until I finally understood one Issue Type Screen Scheme per project.

0 votes
Henrik Gehrmann December 30, 2013

Ah, got it. Basically have to go to 'Configure Issue Type Screen Scheme' and associate multiple screen scheme (one per issue type). Then use that 1 Issue Type Screen Scheme and associate it with the project.

Thanks all for the quick response!

0 votes
darylchuah
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 30, 2013

Hi Henrik

You can basically create Issue type screen scheme, allow you to associate to different issue type which will then map to a particular project, for more information on the relationship between field and screen, you may refer to the following documentation:

0 votes
Vishnukumar Vasudevan
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 30, 2013

Suggest an answer

Log in or Sign up to answer