Relinking/Updating moved Jira Requirements

App Feedback
, , ,
1

Hey Testiny

Recently we were updating some test cases with requirements in Jira where we had moved the linked work item in Jira from one project to another (i.e. Issue AVC-123 moved from project ABC to DEF, and is now issue DEF-456).

Testiny would correctly show in the requirements tab that the issue doesn’t exist with the old ID. But when we tried to link to the issue with the new ID, it wouldn’t show in the result filter. I can see in the network requests in the browser console that it is able to find the issue using the new ID.

However, if we removed the old reference it would then show in the result filter.

This flow is somewhat awkward, as there’s no explicit indicator of what is going wrong. Would it be possible to fix this, such as by:

  • Automatically updating the issue ID when the issue is moved in Jira
  • Allowing us to add the issue using the new ID without having to remove the old ID, or
  • Indicating that the issue is already linked (thus hinting we should remove the old reference)
2

Hi Ben,

Thanks for reporting this issue!

The filter for already linked work items is too aggressive. We will fix this so moved work items will show up to be linked again.
The fix will be in the next release, so it should take just a couple of days to be available.

Best regards,
Alex

3

The fix has just been released:

Best regards,
Alex