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

Sub-Task ID CSV import

I would like to import (using the CSV importer) the following:

1. Issues

2. Sub-Tasks related to these issues.

However, I want to RETAIN the original Sub-Task ID and not have a new one created.

So ...

XXX-1234 is the Issue ID

abcd-1234 are Sub-Tasks of the Issue ID

efgh-1234 are Sub-Tasks of the Issue ID

I want to import using CSV these Sub-Tasks and have them associated with the Issue ID as abcd-1234,  efgh-1234 and not a new issue-keys e.g. ijkl-1234.

I hope this makes sense to somebody.


1 answer

0 votes

There's a couple of things wrong here.

First, a new issue always takes the next free number in the project, you cannot set issue keys.  (You can give Jira the issue key, but that tells it "edit existing issue if there is one")

Second, your issue keys are invalid so it can't work anyway.  Sub-tasks belong to parent issues, which belong to projects.  By definition, a sub-task is in the same project as its parent, and hence have the same project key.  Your issues would have to be

  • XXX-1234
  • subtask: XXX-1235
  • subtask: XXX-1236
  • (and obviously, you can have gaps - XXX-1400)

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

303 views 1 3
Join discussion

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