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?
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.
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?
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.
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!
Recommended Learning For You
Level up your skills with Atlassian learning
Learning Path
Get started with Jira Software
New to Jira Software? These short, self-paced courses will teach you what you need to know to get up and running quickly.
The Beginner's Guide to Agile in Jira
Learn what agile, kanban, and scrum are and how agile works in Jira Software.
Realizing the Power of Jira Reporting and Dashboards
Use out-of-the box reporting and dashboard capabilities to view and assess progress and bottlenecks within projects.