We had 5 custom fields on a project and some issues entered data for those custom fields. Now, going forward i do not want users to view those custom fields. So , what i have thought of is to remove those custom fields from the custom field context.
Is it the right approach to limit custom field visibility at project level or would you recommend creating a new issue type screen scheme for that project and removing it from the screens(leaving custom field context as it is).
My concern is what will happen to those issues which has data against those custom fields after i make the change?
To address the last bit of the question, if you change field configurations, context, screens, or anything else, then the data within the fields becomes inaccessible.
But not deleted. You have to deliberately blank the data out, or delete the field completely in order to destroy the data stored against issues.
You could use a Field Configuration Scheme to simply hide those fields in all projects that are associated with this field configuration.
You can read more about the field configurations here :
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...
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!
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