I do not understand the purpose of a screen scheme. Is there a simple example that shows how someone would use them? The Atlassian documentation shows me how to create a new screen scheme, but I have no clue why I want to do that.
Screens are a collection of fields that you want to show to a user at some point.
A screen scheme collects them together, defining a screen for Create, another for Edit and a third for View. This is quite handy because it means you can do things with different fields.
For example, you can have a "Create bug" screen that includes version it was found in, but then have an "edit" screen for it that lets people add the data about which version it was fixed in and what the package release is.
Then, alongside that, have a "Create incident" screen that only asks for the basic details, and then later in the prrocess of fixing and analysing it, you introduce "root cause" type fields
You need one screen scheme for each type of issue you wish to behave differently. I usually keep the screens separate, but you can share them. For example, you could have screens as follows:
View all (which contains all the fields from both issue types)
Then your screen schemes could say
Except I left one bit out. A screen scheme also has a fourth screen, which is "default". This is set to the screen you want to use if you don't fill in one of the other three. It's just a way of shortening the list though. An example here would be
Because we have not set View or Edit, those actions will use the default, Bug edit screen.
Personally, I tend to call them out explicitly every time, so my scheme would still look like:
They both work the same, but mine is absolutely clear to a new admin
You'll be glad to hear all the other scheme stuff is more simple. Screens are the only ones with three layers at the moment, and I like this table (it's not naming all the schemes, its a sample)
|Project level||Issue level||other|
|Issue type screen scheme||screen schemes||four screens|
|Field config scheme||field config|
|Issue type scheme|
Screens are a JIRA concept. They are part of the JIRA Core product, which are then used by the Service Desk application.
In JIRA, there is the idea of a Create operation, an Edit operation, and the View operation.
So, some tips –
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...
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