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.
Hi! My name is Eoin and I'm a product manager working on Team-managed projects in Jira Software Cloud. We're continuously improving and updating Jira Software and feedback from our customers is ...
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