Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Can populated fields be displayed if that field is not in the Screen Scheme?

Meagan Marwitz
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 10, 2024

Apologies if this is a low-level question -- I am fairly new to using Jira and am still learning all of the admin functionalities.

I recently moved to a new team using a new project in Jira, and they have been using the same screens and screen schemes for all issue types. I have learned how to create new screens based on these issue types, but I am worried that previously used fields will no longer be visible once I introduce a new screen scheme. For example, I no longer want "Acceptance Criteria" or "Design Assets" to be fields for Bugs, but these have been used in the past.

Is there a way to keep all fields visible that had previously been filled in, but only allowing users moving forward to stick to the newly established screen scheme?

1 answer

1 accepted

3 votes
Answer accepted
Walter Buggenhout
Community Champion
May 10, 2024

Hi @Meagan Marwitz and welcome to the Community!

A screen scheme consists of 3 screens, one for each issue operation:

  • create
  • edit
  • view

If you set up different screens for viewing issues and for creating/editing them, you can resolve your requirement. Keep the old fields on the view issue screen, but remove them from the create/edit screen(s). That way, you will indeed be able to still see the old values, but users will no longer be able to enter new / update values once you apply the new schemes.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events