Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Update Components in Epics?

Edited

I have imported several Epics in Jira but forgot to update Components field. I have tried to update existing Epics using a CSV file with the following fields:

Summary, Epic Name, Epic Link, Component, Issue Type.


The problem is that when I am using the import CSV functionality, Jira tries to create new Epics and not update existing ones based on the Epic Link.

Any suggestions ?

1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 28, 2022

Hello @Konstantinos Antonakopoulos 

If you are trying to update Epics, using Epic Link is the wrong field to use to identify the existing Epics.

Epic Link is the field used in a child issue to record the issue key for that child's parent Epic. The Epic Link field is not used within Epic issues.

You need to include an Issue Key field in your CSV, and provide the issue key for the Epics you want to update. In the field mapping process, map that to the Issue Key field.

Thanks Trudy!

I will try this tomorrow and let you know.

Hi @Trudy Claspill !

It seems that it worked. The only fields required to update the Components field were Issue Key and Summary during the import. 

Seems that Summary is required along with Issue Key.

 

Thanks again!

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 31, 2022

Yes, that is correct. When you use the CSV import to update an existing issue you have to provide the issue key, summary, and any fields you want to update.

tabish.mohammed
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!
Sep 07, 2023

Bulk change feature helped me changing the component name for an epic.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events