I've got a custom Issue Type that is currently included in the Issue Type Schemes of 3 Projects.
I.e., ABC: Kanban Issue Type Scheme DEFAULT
I have made new custom fields, and a new custom Screen, Screen Scheme (create, edit and view), and Issue Type Screen Scheme for my custom Issue.
I do not know how to implement the new Screen so it is visible whenever I create, edit or view my custom Issue within these 3 projects.
The 3 Projects also have all the standard Issue Types (Story, Epic etc), plus my custom Issue Type.
If I go to one of the Projects, and go to Settings / Issues / Screens.
There I find:
ABC: Kanban Default Screen Scheme DEFAULT
ABC: Kanban Bug Screen Scheme
My options are to either edit or replace the Screen Scheme. (I cannot see how to add another Screen Scheme. If I could, I would then take my custom Issue Type out of the default Screen Scheme)
If I go to Edit (the default Screen Scheme), I have the option to 'Associate an issue operation with a screen'. The actions available are Create Issue, Edit Issue, and View Issue, and below this select field I can pick the new Screen.
However, if I select 'Create Issue', and then select my new custom Screen, I have to assume my custom Screen will then be used to create all of the Issue Types associated in the Issue Type Screen Scheme?
I don't want my custom Screen to be used for a new Story etc., just for my new custom Issue Type, this is not the answer I'm thinking.
If I replace ABC: Kanban Default Screen Scheme DEFAULT with my new custom Screen Scheme I made for my custom Issue Type, then it will also be used for Story and Epic, and all the other Issue Types?
Recap: I need to display certain custom fields arranged in a certain way for a certain Issue Type within certain Projects. I don't want the Screen to become the default for the various actions of any of the other Issue Types within the Project.
How do I do this?
Thank you
EDIT: I have tried 'Associate an issue operation with a screen' when editing ABC: Kanban Default Screen Scheme DEFAULT, and indeed it did set that Screen for every Issue Type when performing the action.
So the solution will not come from editing the default Screen Scheme of a Project.
... in Project / Settings / Issues / Screens
I selected: Actions / Use a different Screen, which brought me to the 'Issue Type Screen Scheme Association, This page allows you to associate an issue type screen scheme with the project' page.
Then I selected my new custom Issue Type Screen Scheme.
This took away the 'ABC: Kanban Bug Screen Scheme' below the default Screen Scheme in Project / Settings / Issues / Screens, and replaced it with my custom Screen Scheme, so now my new custom Screen is shown when creating/editing/viewing my custom Issue Type, and the default Screen is shown when doing actions with all other Issue Types.
The question now remains - why is a Project forced to only have 2 associated Issue Type Screen Schemes?
Because the Bug Screen Scheme is gone, now replaced with my custom Screen Screen.
I have another custom Issue Type I was going to do up another Screen for, also in the same Project, but what is the point if 'This project uses 2 screen configurations.' maximum.
This a setting somewhere?
The options or the process has somehow changed, so now I can associate unlimited Issue Types with whatever Screen Schemes from the Actions: Edit option in Project / Settings / Issues / Screens, then go to Associate an issue type with a screen scheme.
Learned a lot the last two days!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have no further how-to questions at this time, thank you (pending further investigation into various processes)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.