You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi Community,
during a migration with Configuration Manager for Jira custom field "Story Points" got own contexts for each migrated project.
I learned deleting a context would destroy values saved in the corresponding custom field for all affected issues.
We deleted the context (ACCOUNTING) anyway and noticed nothing was lost (we even let a full-forefound re-index follow for the instance). This is great - and actually it means there is no problem at all - just the question why is that?
Is it because it is a plain number field (not checkboxes and the like) and the project is now using the global context?
I would have expected that the project assigned to the "ACCOUNTING" context would lose values in custom field "Story Point" for all issues.
It is Jira Server 9.4.
Best regards,
Birgit
Hi @bschmi ,
The field values will bit get deleted from the database when you delete a context from JIRA. The custom field table holds this value and when JIRA issue satisfy a new context, it shows the field value on the screen. In your case, you have deleted the field context ACCOUNTING, but enable global context to allow the project to show the value on JIRA screen.
I hope that make sense!
Thanks,
Ojase
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.