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.
Many thanks
Mick
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:
https://www.gurock.com/testrail/support https://www.gurock.com/testrail/about/contact
Calling numbers:
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.
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.