what are the benefits of using different screens for edit, create, view

[Donna Macauley]

This question is in reference to Atlassian Documentation: Associating screen and issue operation mappings with an issue type

what are the benefits of using different screens for edit, create, view

[Jonas Andersson · Accepted solution]

I allows you to not clutter every screen with information you might just need when creating the issue. An example is a bug-issue type where you might just want to have a summary, version and description of the issue. As the case goes into research you might want to expose a worklog, and as you close the issue the summary and description of the issue should already be correct and you might add fields that allow you to retrospect over the issue to evaluate your own work, and how you could have done it better. While editing, editing most of these fields might be useful or not.. It just to be able to fit every organization.

[Donna Macauley]

I get the less fields on the create screen, that makes sense. Can you give an example of how it's beneficial to have different View and Edit screens? 

[Matt Doar [ServiceRocket]]

Imagine I have a field named Root Cause that is used when a bug is fixed to describe what caused the bug.

I won't know what value to use in that field when I create a Bug

So there is not much point in having the Root Cause field on the Create screen for a Bug

[Donna Macauley]

I understand having a separate Create screen. What is the benefit of having two different screens for View and Edit? So a total of 3 different screens.