Jira Spoke how do you move issues between Jira Boards using the integration

[kmolson73]

We are currently using the Jira Spoke to integrate our records in ServiceNow to Jira (bi-directionally for updates). Our users would like to be able to change the assignment group on the record in ServiceNow and for it to automatically move it to that new assignment groups board/project in Jira. I am not seeing a spoke that specifically does this. The only way I have been able to get it to work so far is to clear out the correlation id in SN and then my flows pick it up under the new group and creates a new issue on the new board. This issue with this is that the old issue that was in Jira is still there and it only gives me the options of leaving it be or setting it to done. The users do not like this option or the duplication and would just like to move the issues between boards. Some users work more in Jira and others more in SN so having this work bi-directionally would be best. 

Any ideas on this? 

[Dominik11]

Hi,

i have no solution for your question but you maybe answered mine already. Is it possible to move synced issues from one project board within Jira to another one within another project and is the related incident in servicenow updated correctly? For us there is no need of changing the assignmentgroup afterwards..

would be great hearing from you!!

[kmolson73]

Here is how we did it, although it may not be the best way it was how I got it to work. 

I created a table in the Jira module in SN to house the list of assignment groups that sync with Jira (which is mostly our IT groups) those records contain the Jira project name associated to that group, Jira project code and epic link ID if they have one. I have a Flow that triggers when the assignment group changes in SN (and correlation id is not empty). In the actions it looks up the record in that Jira data table I created and if a record is found for that assignment group it updates the record in SN removing the correlation id. By doing that it will then kick off my regular flow that syncs a record to Jira for the new assignment group. In Jira basically it is creating a brand new record on the new project board (not all our boards have the same status columns so this worked best for us) and it deletes the old record on the previous board. You could however have it just close the old record rather than delete in, in our case the groups did not want it sitting in their closed list as in most cases it was just assigned to the wrong team. 

Also, to note in SN when we implemented the sync process I created a tab on the records in SN that only shows when the correlation id is not empty that houses the Jira details (project name, id, assignee in Jira, jira status etc. as well as I added links in that tab to the Jira record). 

[Dominik11]

Great, thanks a lot for that quick reply.

What I am interested in in special is: if in Jira somebody moves an issue (connected to an incident in Servicenow) from one project to another project, will this automatically update the incident in Servicenow (project key / jira url)?

[kmolson73]

I would think you might be able to do that but so far I haven't been able to get that to work. It just breaks the link for the sync in my case.