The problem is that we move a lot of issues between projects which changes the key so we need a unique ID that we can share with the customer for tracking purposes.
What is the best way to solve this problem?
Is there a way to display the issue ID on the screen? I believe that the unique ID is visible if you hover over the edit button but it is not a user friendly solution.
You could simply still give your customers the original issue key. Jira takes care of redirecting to the appropriate issue in case it is being moved to another project.
If you want to rather go with the id, @Esther Strom's automation tip is a nice one.
I could think of following this procedure:
You might want to think about setting a direct link into your custom field like: https://xxx.atlassian.net/issues/?jql=id={{issue.id}}
Cheers,
Matthias.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You need to create a custom field and put the number in it. It would be best if you use a transition to assign the number and then only put it on the view screens.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Alternately you can use the new automation capabilities to do this, although depending on how active your instance is (and whether you're on Standard or Premium) you may run into execution caps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.