The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Migrate field content to another field

Bassant Gamal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 17, 2022

Hello everyone, 

I've been struggling with configuring each issue type "field configurations", so I used the field [Description] to contain my User Story headline. 

 

Now I that I figured out how everything goes, I created another custom field with label [User Story] and I hid the [Description] field from the Story issue type. 

My problem is that now I want to migrate the content of [Description] field for all previously created story issues - to the new custom field [User Story].

Is there a way to do this action in bulk? 

Thanks for your help in advance :)

1 answer

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

1 vote
Answer accepted
Walter Buggenhout
Community Champion
June 18, 2022

Hi @Bassant Gamal and welcome to the Community!

Probably the best way to do this in bulk, would be exporting your issue key and description to a csv file and then re-importing that same file again, mapping the description to your new custom field. For more details on importing data from csv, see this support article.

On a side note, description is a system field in Jira and - in general - perfectly suitable for describing your story. It is considered best practice to use existing fields where possible, rather than creating additional custom fields for every slightly different variation of a same concept. You have the risk of ending up with all kinds of different fields in your configuration that basically are all doing the same thing. Don't get me wrong - you can perfectly do what you are doing, but it may not be really necessary or scalable in the long run.

Hope this helps!

Bassant Gamal
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
June 18, 2022

Yes very clear, Thanks alot @Walter Buggenhout

 

Regarding the description field - As jira admin, can I change its name?

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events