Best Practice for storing External IDs

We're migration to Jira! As part of this migration, we will be linking customer support tickets (SRs) that are in an external system to Jira Issues. There is a m:1 SR:Issue relationship. Any suggestions on the best way to store these IDs? Options considered so far is a Text box with ;-separated numbers. This isn't too interactive though. Also thinking about another Issue type where the SR number is stored in the descrition (all other fields hidden) and then using the built-in related issues functionality. This might be more flexible in the future (adding URLs etc).

Any other options?

Thanks

Jacques

1 answer

1 accepted

Accepted Answer
0 votes

For me the question here is, how will you use these SR IDs (reports, etc.. you'll need based on SR id or SRs per issue)? Then you can descide what's the best option to store them.

Apart from the suggestion above - you may use a Labels Custom field, so you do not have to use a separator like ';'.

You can also create issue links from the issue to the SRs as issue links allows creating Web links pointing to any URL.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

21,562 views 2 7
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you