Freeze Closed Issues so that they do not inherit new changes made to their Tracker type (e.g. additional or removed custom fields)

Added by G Yates 4 months ago

Hi,

As a Redmine administrator I have a requirement to change a longstanding Tracker type by adding and removing custom fields.

At the moment if I do this and add or remove custom fields from a Tracker these changes are also made to historical Closed Issues of this Tracker type, and if viewed, historically relevant fields will be hidden.

However, it would be preferable to 'freeze' historical Closed Issues and only have the Tracker changes apply to currently Open instances of the Tracker type, so that historical Issues will look identical to when they were closed.

Is this possible and if so how can it be achieved?

(I am currently using Redmine 3.2.6.stable)

Thanks in advance!

Glenn.

Replies (2)

RE: Freeze Closed Issues so that they do not inherit new changes made to their Tracker type (e.g. additional or removed custom fields) - Added by Guillermo ML 4 months ago

Maybe you can:
  1. Rename the actual tracker as "Old Tracker".
  2. Create a new tracker with the original tracker name and the custom fields required.
  3. Filter the issues, showing only the non closed ones.
  4. Bulk edit those issues changing the old tracker to the new one.
  5. Disable the old tracker so nobody can create new ones.

RE: Freeze Closed Issues so that they do not inherit new changes made to their Tracker type (e.g. additional or removed custom fields) - Added by G Yates 4 months ago

Hi Guillermo,

Thanks for your suggestion which looks like it should work (though not as straightforward as a setting which I hoped might exist to facilitate this with a single tracker).

Much appreciated!

Cheers,
Glenn.

(1-2/2)