Hello there, we are currently using JIRA cloud with custom flows and statuses to manage our full SDLC. The last three statuses usually mean that the developers have finished their work and are waiting for the release team to accept the change, merge it, and deploy it.
In order to notify the release team that a feature is ready we create an RFC (Request For Change) on our Service Desk account and from there they will update the RFC, once it has been closed it means the feature is ready and finally done.
My question is: Is it possible to, somehow, link Service Desk to JIRA so that when a ticket in SD is closed the ticket in JIRA can be moved from status to done? We usually have to be monitoring the SD open tickets to see if they have been closed so we can manually close the tickets in JIRA but it'll be easier and less error-prone to automate this as we usually forget to do so.
So it'll be something like:
JIRA -> Waiting for review (status manually changed)
SD -> RFC is created (the developer goes to the SD instance and creates the ticket)
SD -> A release manager accepts the change and manually changes the status to closed of the SD ticket
JIRA -> The ticket is changed to closed from SD automatically, somehow
As a note: the SD instance is NOT used by customers, we use it only for internal purposes so security here, information-wise, is not an issue.
Thanks in advance!
Thank you for getting in touch with Atlassian Community!
It's possible to automatically close a ticket in Jira SW when a linked ticket from SD is closed.
To make this you will have to use the add-on Automation for Jira. In order to test, you can use the free version.
Just remember that the tickets must be linked for the automation to work.
After installing the add-on, you can configure the automation as below:
Note: On the If: matches you must change the sd1 to your SD project key.
Please, give it a try and let us know how it goes.
Hello @Kathi Paquet,
Thank you for reaching out to Atlassian Community!
It’s necessary to create a global rule.
I tested here and when creating the automation rule within the project, it will only consider tickets from that specific project.
Even though the original question was posted in 2019, the rule keeps the same. Here is a screenshot of the test I made today:
On “No actions performed” the rule was restricted to the Service Management project. Once I changed to “All projects” and added the “If matches” using JQL (project = IT), it worked.
Please, take your time to test and let us know how it goes.
This morning, Atlassian announced the acquisition of ThinkTilt , the maker of ProForma, a no-code/low code form builder with 700+ customers worldwide. ThinkTilt helps IT empower any team in their or...
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