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

How to keep the ticket number when bulk move issues into their new project

Hi,

We want to upgrade our JIRA core to JIRA software. We need to move the issues in JIRA core project to JIRA software project. I searched solution in following URL. 

https://confluence.atlassian.com/adminjiracloud/convert-project-to-a-different-template-or-type-966673096.html

However, when moving the issue to new projects, ticket numbers were always changed. See the picture. How can I keep the ticket number?

Before moving:

original ticket number.png

After moving:

changed ticket number.png

2 answers

I don't see any answers in the above link. Is there a different link with this approach, which seems to provide a working solution as referenced below?

Sorry @Scott Ross  I don't have any other input apart what @John Funk mentions below. That was my thought. The link above just gives the general how to.

HTH,
KGM

Thanks @Kristjan Geir Mathiesen - Servado - my problem was when I clicked on that link earlier this morning, it only showed the question and "0 answers" so the general how to wasn't displayed.  Strangely, I just clicked the link again and now see the answers and the how-to.  So you can now ignore my initial reply! 

0 votes
John Funk Community Leader Apr 24, 2020

Hi Shawn,

I am not sure how you can do that. You can try to follow what Kristjan suggests. You would need to export the full issue, and then import it into the new project using the guidance in the above post. 

But the problem is that the new project MUST have a different code for it - you can't reuse ones. So if your current project is ABC and all of the issues are ABC-1, ABC-2, etc. Then the new project cannot use ABC - it must be something different. 

John Funk Community Leader Apr 24, 2020

I guess you could do the export, then change ABC to ABC2 or something like that - which will convert all of your existing issues. Then create the new software project as ABC. Then import the original ones you exported with ABC. Then you would just delete all of the ABC2 issues. 

I would try that with a handful of test issues you create in a new test project first, including adding some links to other cards to make sure you don't lose the links. 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

298 views 9 7
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