Currently, my organization has Jira Service Mgmt and when request come in that need development work we link the tickets to corresponding project boards for developers. What is the best way to communicate to the customer on the original Service Desk ticket. Right now I have automation set up to transition the service desk ticket throughout the workflow. Another issue we are facing is when we run reporting for the org we are getting duplicate issues (1 from Desk and 1 from the corresponding project board). What are some of the best practices for this type of use case. Any suggestions would be greatly appreciated.
Great question. I believe that this is something everyone struggles with. As far as best practices go the products are set up to integrate well together. Automating the communications/notifications to the customer as much as possible is the best way to go. It sounds like you have this in place. Ensuring proper monitoring and reporting of work is also important and it sounds like this is what you are struggling with a little bit. I would just ensure that you have a solid process in place which it sounds like you do. I would adjust your reporting so you are properly reporting on all the information. You may have to have certain request types or issue types to help distinguish the work and properly report on it. I really think you have everything setup well and to what one might call best practices.
Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...
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