Custom field won't be removed if you changed the tracker to a none-custom-field tracker
Confirmed with Redmine Ver: r2670
- create a custom field
- create a tracker that uses the custom field
- create a new issue using the tracker and enter some value into the custom field
- when the issue is shown click on Move
- Move the issue to another tracker without the custom field.
- Show the issue and the costom field still exists although the tracker doesn't contain the costom field.
I have to remove the custom field from the tracker which dosen't contain it by editing the Database directly.
I think if the tracker of issure is changed, the custom field which is not defined for the tracker should be removed.
Thank you for reading.
Updated by Minjie Zhu almost 15 years ago
Jean-Philippe Lang wrote:
This is fixed in r2724.
I confirmed the revision and it works well!
And I found that this revision just changed the view, but not the data in DB. Because if I return the tracker to the former, the custom field shows the old data.
Maybe it would be nice to clear the custom field of the ticket when the tracker is changed.
But now it maybe good enough. So thank you so much for your help :)