Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,300,353
Community Members
 
Community Events
165
Community Groups

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

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?

3 comments

Mikael Sandberg Community Leader Sep 19, 2019

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.

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. 

@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 Community Leader Sep 25, 2019

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

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.

Comment

Log in or Sign up to comment
TAGS

Community Events

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

Events near you