Are changes to custom "checklist" fields applied retrospectively to old issues?

[mike.howells]

If we have a custom field that holds a checklist and I then change the field to remove an item from the checklist, will that item be removed from all existing issues that use the field, even if it was ticked?

[Cyril Egan · Accepted solution]

From Jira 4.4 onwards you can disable options in custom fields.

http://confluence.atlassian.com/display/JIRA044/Configuring+a+Custom+Field#ConfiguringaCustomField-Options

This stops a user selecting them when creating/editing a new/existing issue. It is still available for searching and reporting on dashboards and filter results.

[mike.howells]

Perfect, thanks!

[mike.howells]

If checklist items are removed from old issues, this makes checklists fairly useless for recording compliance to process. We need to see that people did the right things as defined at the time when they did them. If the list of things to do changes, we don't want that to change what people did before.

Is there another way to record that? At the moment we're recording it in comments because they won't be changed, but it means only one person can tick off all the items in the checklisk.

[Renjith Pillai]

Yes, and I guess Jira warns you while you attempt to remove the value.