Bug in closed issue set to non-editable is still editable

[Salome Brütsch]

Hi

Currently, when a custom field is removed from a screen scheme, it also disappears from issues—including closed, non-editable ones. This results in the loss of crucial data, as users can no longer see the field when viewing closed issues.

This is especially problematic when updating templates in the eQMS. Please vote for this ticket to help raise awareness:

https://jira.atlassian.com/browse/JRACLOUD-92148

Thank you very much!

Best,
Salome

[Rilwan Ahmed]

Hi @Salome Brütsch ,

This is normal behavior of jira.  If you remove the field from view screen, it is removed from all open and closed issues irrespective of the status. When you add back, the field along with its existing value is displayed on the screen again. 

If you just want any field to be seen and not editable, remove them from Edit screen of the issue type. 

If you want any field to be displayed on the screen, they should be present on view screen of that issue type. This is normal jira behavior and not the bug. 

More details about screen is in https://support.atlassian.com/jira-cloud-administration/docs/manage-issue-screens/

Please note:

• jira.issue.editable property key is used to have control over whether the issue can be editable on a specific status or not.
• Add/remove field is part of Project settings and not issue level. 

[Rilwan Ahmed]

Hi @Salome Brütsch ,

Welcome the community !!

I would like to understand, why do you want to remove the field from screens after ticket is closed ? 
If you are removing the field from screen, that means you don't need the field to be displayed anymore.

Can you please explain what exactly is your  requirement and see if Community members can find a solution. 

[Salome Brütsch]

Hi @Rilwan Ahmed 
I actually I do not want that the fields are removed from the closed issues. But this is what Jira is doing. When removing a custom field today the field also gets removed in a closed issue from year 2021. Leading to lost data from a cosed issue.

Lots of users are not aware of this ''bug'' in Jira and Atlassian support mentioned that this is not how Jira should behave, but it does for multiple users.

Do you experience the same?

Please find also attached some images of my experiment, where I removed the custom field ''supplier assessed''.

Please see also here the open ticket: https://jira.atlassian.com/browse/JRACLOUD-92148

[Sai Krishna Yadav Challendula]

Hi @Salome Brütsch ,

The field and its data don't disappear; they simply become hidden. You can still view all fields and values in the issue navigator, for example. However, if you remove the project context of the field, the data will be permanently deleted for that project.

[Prosentti laskuri]

If a closed issue marked as non-editable is still editable, you can calculate the percentage of such occurrences using Prosenttilaskuri! 📊 Track and analyze the percentage of editable closed issues to assess system reliability and improve accuracy. ✅🚀

[Aaron Morris]

@Salome Brütsch -- Thank you for providing the additional context.  @Rilwan Ahmed just gave the correct answer, and I'd just like to clarify it a bit.

To make your "Supplier assessed" field visible on old (locked) records, but not on new ones, try this:

1. Locate the Screen Configuration you shared in your screenshot. (I don't know what the name is from the screenshot.)
2. Make a copy of the screen configuration.
   1. Leave the original name as-is, and name the copy by appending "(View Only)".  For example, "My Screen" and "My Screen (View Only)"
3. Remove the "Supplier assessed" field from the original screen.  Leave (or add) the "Supplier assessed" field on the new View Only screen.  You should now have two screens that are nearly identical, except that the View Only screen contains the "Supplier assessed" field.
4. Next, locate the relevant Screen Scheme configuration. Update the configuration to associate the "View issue" operation with your new View Only screen.  Leave all other associations as-is.

This should solve your problem:

• Older locked issues with a "Supplier assessed" value will display the field.
• Newer locked issues without a "Supplier assessed" value will hide the field.
• Editable issues will hide the field preventing users from adding values moving forward.

Let me know if you have any questions.  I have a lot of experience using Jira as an eQMS, so I definitely understand your concern! :-)

[Aaron Morris]

Cloud is the same as DC in this respect. There's no actual data loss happening.

[Tomáš Vrabec _neresit_cz_]

If you return the field back to screen, will the value re-appear? 

Because Data Center works this way.

Cloud is purging data out? :-D