We are in the process of re-doing all of our screens to have minimized and customized fields during create, edit/view specific by issue type. This is a huge change for us as when we initially started on Jira, our consultant attempted to put us on 1 - multi-use screen so that it was easier to maintain. 2+ years later the screens have gotten bloated and are super noisy with non-relevant information depending on issue type.
Our goal was to start out the year with new screens by issue type, however, we're running a bit behind schedule. Before I make any large changes, I need to be understand what exactly happens if we change the screens, removing lots of fields? I assume that in the cloud the field and value is still there, just NOT visible in the UI. Is my understanding correct?
Meaning:
- If we run a query/filter and include a field no longer in view/edit - we can still filter on the data if it was previously populated? Similarly....
- If we decided we want to add that field back to the screen, the value would appear populated with whatever it had historically? - i.e. - The value is not being deleted in when removing from the screen.
Knowing the answers to the above will help us get testing over the finish line and to be less anxious about such large changes we're making. Appreciate the feedback.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.