Linking Work Items Through Bulk Update

[Jeremy Bingman]

I am attempting to link a lengthy list of Work Items to another Work Item through Jira Cloud. It seems that the bulk update function still does not support this capability.

I found this post which previously offered a work-around solution however, in the most recent update this no longer seems to work. I have taken a list of space- or carriage-return separated issue keys for the work items, pasted them into the field to link them, clicked out of the field and the pasted values go away. I have paged them into the field and tapped the Enter key and Jira transforms them to a string representing a single issue and therefore cannot identify it/them.

I looked into the free Add-On offered in the prior post but, it seems to no longer be available. Does anyone have an updated solution to this?

[Jan Westphal]

Hello @Jeremy Bingman ,

you might be able to use a Jira automation. You can manually trigger an automation on the issue you want the other to be linked to which will go over all the key you add to the Branch.

This will add a link between each item of the branch to the issue the automation was triggered on.

Best regards,
Jan

[Jeremy Bingman]

Thanks for the suggestion. I attempted and it appears that this will only work if the Work Items are all within the same project. In my specific case, they cross two projects (create a link from batch of Work Items from one project to a single Work Item from another project). When attempting to do this, the interface adds an implied (and hidden) condition that all of the records must be within the same project as the automation and the automation appears to not be able to be manually triggered from within a different project.

[Jeremy Bingman]

NOTE: It may be the case that doing this across projects requires one to be a Jira administrator, rather than just an administrator on the two projects.

[Jan Westphal]

Hello @Jeremy Bingman

You are right, in this case you need to change the scope of the automation to include both the projects you need. This can only be done by a Jira Admin in the global Automation. The Solution should still work though.