Add custom field statuses (aka, lock fields)
Custom fields can become a mess after a while, and hard to sort through when creating new projects. It would be interesting to have a value like what's used for user accounts to 'lock' custom fields. Just like users, this would hide the fields from project settings, while allowing them to be unlocked rather than recreated.
For project-specific fields, this would be helpful once a project is archived, but allow reuse if a follow-up or related project kicks off later.
If a project stays active, existing data for that field will stay visible, but it will not be possible to update previous values or apply to new tickets. Old values will be protected if a ticket is updated after the field is locked, of course.
Let me know what you think!
#3 Updated by Joshua DeClercq about 5 years ago
Nathanael Hansen wrote:
Would this also be possible with Issue Statuses? They too, can get messy after a while and would be nice to not have every status ever used when setting up queries.
I don't think statuses need something exactly like this. However, queries shouldn't offer statuses that are impossible to use with the trackers available from the query's location. That's just silly, and worth posting a separate ticket for.