Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Update Custom field values without affecting the existig issues



We have the custom field Severity with the values 

  • Critical
  • Major
  • Minor
  • S3 : Major
  • S2 : Critical
  • S1 : Blocker
  • S4 : Minor
  • S1
  • B
  • A
  • C
  • D


we need to customize these values to S1, S2, S3, S4 mapping the old ones like

S1 ----> Critical, S1: Blocker, A, S1

S2 ----> Major, S2: Major, B

S3 -----> Minor, S4: Minor, C

S4 -----> D


When I am trying to create the new custom Context and mapping to the new projects, we have lost the issue data. Could you please suggest the steps to update the values from data base or using script runner.

Thanks in advance.



1 answer


The values of the customfields or customfieldValues have an id and a value for example your value S1: Blocker has the id 190103

This id is the one that relates the issues to the values of the field, therefore in the database a KEY-123 issue has the value 190103 for your CF.

When you create a new context, the fields of that new context have a different id, so if you assign a new (different) context to the project, the new field "S1" will have a different id than S1 of the original context.

Also, since your context does not have the other value and the id is not available, the historical information will be lost.

What this allows is that when editing the name of a value it is updated in all tickets and that is why the values of the custom fields can be disabled but not deleted


Unfortunately if you are going to use a new context you will have to reassign the values to the cf pointing to the new options.

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you