nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Difference between screen schemes and issue type screen schemes?

Anand Vardhan_21ao97

Hi,

Can anyone elaborate the difference between screen schemes and issue type screen schemes? Would be great if it can be explained with an example.

Accepted answers

karim -Atlassway-

Hi @Anand Vardhan

Example you have 3 issue type (Bug , Error , Task) , and you need to have differents screen for each one , so in this case you need to have for each issue type a screen scheme .

Note: Screen scheme contain Create , Update and view ... screens.

So if you have not this requirement , mean you have the sames screens for all issue type , you do not need to get a screen scheme for each issue type .

Hope it's clear for you now

Regards

Gezim Shehu [Communardo]

Theoretically

Screen Scheme - Defines which screens are going to be used for which operation (create, view, edit)

Issue Type Screen Scheme - Defines which Screen Scheme (above) is going to be used for which issue type

Here's an example

You have 2 screens:

Screen A (Summary, Description, Due Date)
Screen B (Summary, Description)

You create Screen Scheme 1 "Screen Scheme A" with

Create - Screen A
Edit - Screen B
View - Screen A

You create Screen Scheme 2 "Screen Scheme B" with

Default (Screen

You create a new Issue Type Screen Scheme "Issue Type Screen Scheme X" with

Default (Screen
Bug (Screen A)

So, as a recap , now when a project has specified "Issue Type Screen Scheme X", on issue type:

Bug - You will be able to set Due Date while creating and also view it, but you will not be able to edit
Any other issue type - You won't have field Due Date at all

Cheers

All comments

karim -Atlassway-

Hi @Anand Vardhan

Example you have 3 issue type (Bug , Error , Task) , and you need to have differents screen for each one , so in this case you need to have for each issue type a screen scheme .

Note: Screen scheme contain Create , Update and view ... screens.

So if you have not this requirement , mean you have the sames screens for all issue type , you do not need to get a screen scheme for each issue type .

Hope it's clear for you now

Regards

Gezim Shehu [Communardo]

Theoretically

Screen Scheme - Defines which screens are going to be used for which operation (create, view, edit)

Issue Type Screen Scheme - Defines which Screen Scheme (above) is going to be used for which issue type

Here's an example

You have 2 screens:

Screen A (Summary, Description, Due Date)
Screen B (Summary, Description)

You create Screen Scheme 1 "Screen Scheme A" with

Create - Screen A
Edit - Screen B
View - Screen A

You create Screen Scheme 2 "Screen Scheme B" with

Default (Screen

You create a new Issue Type Screen Scheme "Issue Type Screen Scheme X" with

Default (Screen
Bug (Screen A)

So, as a recap , now when a project has specified "Issue Type Screen Scheme X", on issue type:

Bug - You will be able to set Due Date while creating and also view it, but you will not be able to edit
Any other issue type - You won't have field Due Date at all

Cheers

Anand Vardhan_21ao97

Thanks!

Anand Vardhan_21ao97

Thanks a ton!

Fahad Siddiqui_ihrjma

Dear Gezim Shehu,

What is issue type and issue type schemes?

lakshmi_fdv506

just a small correction to above answer

Issue Type Screen Scheme

Issue type <-> Screen scheme

hence

You create a new Issue Type Screen Scheme "Issue Type Screen Scheme X" with

Default (Screen Scheme
Bug (Screen Scheme A)

Gregory Pakosz

The confusing part in the original documentation is that it says "Screen Scheme ... OR Issue Type Screen Scheme ..."