You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hello! I'm maybe not going about this the correct way, so please let me know if there is a more efficient way to do this.
We currently have a team-managed project that I'd like to move over to a company managed project. I have set up the new project and would like to clone all the issues into the new project. However, I need to keep the Issue keys the same (the letters can be different, but the numbers need to be the same). In my research, I have not seen a solution to this, so maybe it's not possible?
Or should I be going about this differently?
The only way to do this would be to create the issues in a strict order.
Imagine you've got
That you want to clone and move into a project currently having the last issue as XYZ-10. You will need to
This effectively makes the target project pretty much useless.
So, I have to ask - why are you wanting to do this?
Thanks - I need to move to the company managed project because there is functionality that I'm looking for that is not available in the team managed project. Unfortunately, my QA team is very familiar with the specific issue keys and really need to keep them the same when we move over.
We are building a solution to help you move your Team Managed projects to Company Managed projects in an easy way while keeping your KEY the same. Happy to run you through in more detail what we are building if interested.