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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Dear Atlassian community,
I realise this relates to a third party plugin but wondered if anyone could suggest how I go about maintaining TestRail associations when moving issues from a next-gen project to a classic project.
The issueKey is re-created for the new project I create, when I Bulk Update -> Move the old issues to the new project. This breaks my TestRail associations.
I'm thinking this:
I appreciate any comments or recommendations of a better or quicker way to achieve this.
Hi @Mick Might welcome to the Atlassian Community.
For your current issue (market place tool), all that I can find is the Test Rail support team's link who would be best option at the moment. Kindly reach them at:
US & Canada:+1 713-533-5000
Germany:+49 (30) 56796604
If my post is helpful kindly upvote and "accept answer" for the benefit of new members.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.