Can issue forms be changed without influencing completed tcikets?

[Leon]

I am quite a new user to JIRA, and ran into an issue today of which I am not sure how to cope with. 

We store our (CAPA) issues in JIRA in line with our Standard Operating Procedures, however, as I am updating the Procedure, I am required to remove some fields in JIRA to for this revised SOP. However, when removing a section, it removes it as well from all stored tickets (effectively destroying my quality records). This is something that I cannot do. 

So can I change a screen (e.g. removing fields), without this affecting any of the previously stored (closed, open etc) tickets? and if yes, how?

I refuse to believe I would need to create a new project for this purpose.

Thanks a lot for any help!

[Steve Thornhill · Accepted solution]

Yes, If you modify the screens in use for that project you can add/remove fields. Goto the project configuration and locate the screens section to view which ones you need to update.

This will not remove any previously stored data.

However, this will mean that any previously stored data for existing issues may not be visible, unless you have the fields showing for the 'view' issue

[Leon]

Thanks for your fast feedback. The reason behind my question is that I need to have always visible and unchanged records for audit purposes.

One of the CAPA fields in my issue form is the root cause analysis. If I remove this text field and replace it by another type of field (e.g. selection box), the text field will have disappeared from my older tickets and been replaced by the selection box.

I don't know how I can make such (no longer shown) fields visible using the "view" issue for older tickets? 

[Steve Thornhill]

As long as you remove the fields from the create/edit screens then users will not be able to add to them or update them.

Leaving the view screen with the field will allow any existing data to be displayed. If you already have these fields in use and can see the information, then the view screen already has the field set.

Just to add an additional point, any changes to fields are tracked in the audit log of each issue.

[Leon]

Thanks for your help, I will give it a go and try some tests to start understanding the exact functionalities!