Can Gitlab for Jira Cloud support multiple Jira IDs in commits?

[Dan Driscoll]

Is integration limited to one Jira ID for a body of work, or does Gitlab for Jira Cloud support mapping to multiple Jira IDs?   I suspect the former - one body of incremental work  - one Jira.  But wanted to confirm. 

(apologies for also posting in the general Jira questions community - could not figure how to move it - this one seems more apropos)

[Josh_Unito]

@Dan Driscoll my understanding is that the GitLab for Jira Cloud app allows you to send comments from GitLab to Jira to send comments, view issues, change the status, and close issues by including the Jira ID in your command. 

I haven't tested it, but I'm pretty sure you can apply commands to multiple Jira IDs just by separating the IDs with commas.

What's the use case you're interested in?

If you're looking for a more flexible integration, you can also try Unito's 2-way integration for Jira + GitLab. It allows a lot more functionality for cross-tool collaboration (you can enact changes on either end from the other with real-time updates). Here's a guide to syncing issues between Jira + GitLab.

[Dan Driscoll]

The use case is to see Branch, Merge Request, and Commit activity in the Developer Details section of a Jira ticket.      I've read where other Atlassian products support the comma delimited IDs, but not Jira itself.      Not specifically interested in "comments, view issues, change the status, and close issues" but if those are things that developers do in bulk or for multiple Jiras from over in Gitlab, then it would be good to know if they all behave the same.