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

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?

3 answers

1 accepted

1 vote
Accepted answer

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

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.

Perfect, thanks!

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

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.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 27, 2018 in Portfolio for Jira

Introducing a new planning experience in Portfolio for Jira (Server/DC)

In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to   have–in   order to produce a reliable long-term roadmap. We're tur...

2,407 views 15 19
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you