Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Unique Issue ID...where do we stand?

Hi,

Problem: When moving an issue from one project to another, the ID changes.

Expected system behavior: to ease traceability, the ID would remain the same after moving.

Comments: I need to know where we stand in May 2017 in terms of having access to a unique issue ID. It was first reported in 2003 and 2004 and I assume that it has been corrected since then because this is major.

2 answers

Unfortunately, this is not possible apparently. The project key purpose is to tell which project the issue belongs to. Reference here: https://community.atlassian.com/t5/JIRA-questions/Move-issue-between-SD-and-non-SD-project-maintain-Issue-Key/qaq-p/454487 

Thanks. And what about another issue attribute, which could be unique? This could be a workaround. Any idea?

@pascal Bouchard,

The *ID* actually doesn't change, but you will change the *Key* when an issue moves because the *key* must match the parent project.

You may consider if the need for movement across projects indicates that Components should be used instead, or if you feel the need to move tickets across projects is legit, but want to search you can always search by any of the historical keys, and JIRA will still find it, and never reuse a previously used key.

Screen Shot 2017-05-11 at 2.23.49 PM.png

Moved to:

Screen Shot 2017-05-11 at 2.24.28 PM.png

But still searchable.Screen Shot 2017-05-11 at 2.30.07 PM.png

This is exactly the workaround I was looking for. Thanks for the detailed answer. I appreciate.

 

I have an issue identified RM-6.

For test purposes, i have done the following:

I typed key = RM-6 in search field of JIRA Agile but it did not return any value.  

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

230 views 3 6
Read article

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