Issues - Configure Screen Scheme >> Associate an issue operation with a screen
When I select this - I see a current association with a screen ("Demo" = live project).
If I select a new screen (LSHD - test project) - does it break the current association?
Is it a 1:1 or can it be a 1:many ratio?
It might do, but there's not enough information in your screen shots to tell us.
The question is if you are in the same "screen scheme" in each screenshot. If they are separate screen-schemes, you are fine. If they are the same screen-scheme, then yes, you will be replacing what "create" uses.
They are in different screen-schemes.
But in "Configure Issue Type Screen Scheme (for LSHD: Jira Service Desk Issue Type Screen Scheme") - I added the 2 Issue Types I needed and now I see the LSHD: Jira Service Desk Issue Type Screen Scheme in 2 Screen schemes - the bottom one (Demo) is live.
Will this affect that project? I am not understanding the "screen scheme" and "Issue type" screen scheme clearly in my head.
Sorry for the delay in response, I am not the most organised of people.
Short answer: "They are in different screen schemes" means you are doing the right thing and you will not break the associations. (And, as reassurance, even if you missed it and got the wrong scheme, you will not have done any lasting damage to your data, you can simply change it back)
To try to explain a bit more:
I think in layers of complexity in Jira project configuration. It's all about the schemes. Schemes tell a project how to behave. There are three layers of complexity:
So some examples ("examples" because I might miss a couple - I'm tired today)
Note that in group 3 there is only one thing, and it's what we're here for.
An issue type screen scheme has four things to think through:
This seems complex, and, frankly, it is. It took me ages, and a lot of questions on this Community forum's predecessors to get my head around it. I'm told I make it look easy when I'm showing it to people in real life, but I have still not managed to hit on a good document that explains it well enough for most, and I still remember struggling to understand it when I inherited my very first Jira (2.1-ish?)
But it gives us a huge amount of flexibility across projects and issue types, and the fact that it hasn't changed in well over a decade tells me that while it feels complex, that complexity could only be reduced at the cost of loss of flexibility.
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events