I am very confused by the information on the website and I am still unsure of the workflow for this. What I am trying to do is:
- Create a custom issue type in a Project
- Specify the fields that show up when that issue type is selected within the Project
A project have only one Issue Type Screen Scheme, but can have many Screen Schemes under that Issue Type Screen Scheme.
In a Issue Type Screen Scheme, we will specify Screen Schemes for particular issuetype.
like ScreenSchemeA for Bug
ScreenSchemeB for Task and soon.
In a Screen Scheme, we will specify Screens for particular operation.
like Screen1 for Create
Screen2 for Edit
Screen3 for View
In a Screen, we will give fields(include system fields and custom fields)
check https://confluence.atlassian.com/display/JIRA/Associating+Screen+and+Issue+Operation+Mappings+with+an+Issue+Type#AssociatingScreenandIssueOperationMappingswithanIssueType-Associatinganissuetypewithascreenscheme for selecting screen scheme for each issue type.
first you would need to associate your issuetype with the issuetype scheme used in your project.
Second, create your fields, add them to a screen, add this screen to screen scheme (for varoius issue operations). Then map this screen scheme to the issuetype in an issue type screen scheme and associate that with your project. That is basically it.
Having the same problem.
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
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?
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:
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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