Oops, sorry Joe, I didn't read the question like that, but it makes more sense than what I was guessing at. Jira won't import issue ids you give it because it creates issues sequentially in the project. The only time an issue id is of use in an import is when it is the id of an existing issue in JIRA and you want to *update* that issue, not create a new one. As Joe says, to preserve your "foreign" non-JIRA ids, map the issue id into a custom field.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs