Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Hide a custom field from screen but not affect existing resolved changes

Sam Evans
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!
January 12, 2024

Hi everyone and happy Friday.

I would like to edit a custom field in my 'Change' issue type from standard to Rich Text so i can add pictures.

Looks like the only way to do so is by creating another field and hide the previous one.

The field is 'Test Evidence' but understandably i don't want to remove this from closed issues.

Is there a way to have the custom field remain on closed issues? but hidden for new issues so i can create a new field with a similar name so there are no duplicate fields?

3 answers

1 vote
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
January 12, 2024

Hi @Sam Evans 

Is the current type Custom Field a text field and the new field will also be a text field?

Then you can also see the field configuration and change the renderer of the field.

See here for changing the renderer

Or does the new field uses another type of field type?

0 votes
Arensa Prasta January 12, 2024

you can keep it but at the issue layout can choose hide it when empty, so for the new ones you only show the new field. 

0 votes
Eugenio Onofre
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
January 12, 2024

Hi @Sam Evans

Welcome to the Atlassian Community.

You can achieve it by hiding the old field from the "view" and "create" screens in your active screen scheme, but leaving it for EDIT. This way, you will ensure the information is still stored and you can see it on filter results for example.

About the new field, since they have different names, you will not have any issues in having a similar one.

Please remember to accept this answer in case it helps you resolve your questions as it may also help other community members in the future.

Best Regards,
Eugenio

Suggest an answer

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

Atlassian Community Events