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; } } }

Default Screens do you need it if each issue type as creation and edit screens?

Aaron Geister

So how do most of you do this do you create a creation screen and edit screen for each issue type and eliminate the use of the default screen?

Right now I have creation screens so that most custom fields are only on the screen they need to be but some are populating on other screens during creation because they have to belong to the default screen.

If we make the scheme for the creation and edit screens will that eliminate the use of the default screen?

Comments

Mikael Sandberg

The default screen is used for unmapped issue operations, so if you have defined screens for create, edit and view then you do not need the default one.

I usually only define screens for create and edit and leave the default one, and in some cases I only use the default one if the project do not require different screens for the three issue operations.

Aaron Geister

Thanks for the good response.

I was gathering what you said to be correct but wanted to ask in the community to see what best practice is. I am in the process to create the edit and view screens to follow best practice. I have created the creation screens for all issue types we use and offer users. I also have the schemes set up for each issue type so I can add the edit and view screens to them.

Thanks again I love this Community of people.

Aaron Geister

@Mikael Sandberg

I just want a double verification. Once you add a default screen for each issuetype screen and they all have a creation screen, edit , and view the default screen for the project can be removed. Correct? I don't want to remove the default screen for our service desk project till I am sure it won't break something. Or would it be smart to leave the Jira default fields in there just in case some are not showing on issue types I may have missed?

Mikael Sandberg

Correct, if you defined screens for all three issue operations you could remove the default screen.

Lora Lozano

I also would like double verification. If the Create, Edit, and View Screens are all the same, is it not necessary to associate issue operations with them? Will the Default one will handle it as well as unmapped operations?

Thanks in advance.

Liz Ramsey

Yes, the "Default" assignment would cover all operations, so you could remove the screen assignments for "Create", "Edit", and "View", and just use the "Default" screen, if it's all the same screen anyway!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-desk

jira-service-desk-cloud

jira-cloud