How to set up a project with multiple issue types with unique sets of field tabs

[Jonathan Libov]

I am befuddled at how to do something which should be really simple. I have a project where:

• I want to include multiple issue types
• Each issue type should have a unique set of fields

It's that simple, and yet it seems like no matter what I do I end up with issue types whose set of fields are irrevocably coupled, meaning that whatever set of fields I have for one issue is linked to the other. How do I avoid this?

[Daniel Davkovski]

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

[Kevin Lauscher]

This is an incerdible guide.  The way Jira does things is nuts.  Thank you!

[Diego Castellanos]

Hi @Daniel Davkovski, 

I tried to do this and everything works for me, except that I want to make this for a subtask issue type, but seems that I cannot create an Issue type Scheme containing a subtask :(. 

Can you think of a workaround for this?

[Nic Brough -Adaptavist-]

What is stopping you creating an issue type scheme with a sub-task?

[Diego Castellanos]

It requires at least one standard type, but I only need to have the sub-task type. Besides, it only allows adding one issue type scheme per project apparently.

[Nic Brough -Adaptavist-]

Yes, that's because a scheme without any issue types in it would be useless.  It would mean the project could not have any issues in it.

In turn, that also means you couldn't create sub-tasks even if they were in the scheme.  A sub-task is part of a parent issue, but you don't have any of those in your project, so there's nowhere to create them.

The issue type scheme is for telling the project what issue types to offer.  I'm not sure why you're trying to create one that only has sub-tasks.

[Fadoua]

@Jonathan Libov

You will have to go to the Admin Console, under issues you will have to:

• Create a screen for each issue type
• Create a field configuration for each issue type
• Then apply the field configuration to the screen

More help let me know and i will try to put it step by step.

Best,

[Jonathan Libov]

thanks but I just tried that and got the same result. Now all three issue types in the project are syncing field types with one another :-(

[Fadoua]

Will it help you @Jonathan Libov if I send you step by step on how to do it?

[Jonathan Libov]

yes absolutely @Fadoua, thank you!

[Fadoua]

@Jonathan Libov

I am assuming that you created the screens with the fields in them?

Go to Fields -> Custom Fields select one field and then click on the Cog on the right side of the field.

Select Configure then click on "Edit Configuration"

You want to make sure that the issue type is available:

[Fadoua]

@Jonathan Libov

https://confluence.atlassian.com/adminjiraserver073/project-screens-schemes-and-fields-861253368.html

[Jonathan Libov]

thank you but no luck

[Fadoua]

hmm that is weird, something must be configured wrong way @Jonathan Libov

[Jonathan Libov]

is it because these two issue types have the same screens? if so how do i change it? @Fadoua

[Fadoua]

@Jonathan Libovnot sure how I can help next, I can get another champion involved see if they have a better way than mine 😉

[Fadoua]

Yes @Jonathan Libov if two issues are using the same screen there is no way you will get the expected results you are looking for

You have to create a screen for each issue type

[Jonathan Libov]

ok now we're getting somewhere! how do i edit the screen for an issue type though?

[Fadoua]

@Jonathan Libovsorry I was in a meeting. Let me send you how to do it

[Fadoua]

By using issue type screen schemes @Jonathan Libov