We've set up a new Jira Service Desk project on our Jira Cloud account and it's pretty much out-of-the-box settings as far as workflow is concerned. We're seeing that when a ticket status changes, it's putting my user as the one to have changed the status and not the user that actually changed it.
For example, a ticket came in and co-worker of mine decided to work on it. He changed the Assignee to himself, he asked the customer a question in the comments, and then changed the status to "Waiting for Customer". In the ticket history, it shows that he is the assignee, that he made a comment, but that I changed the ticket status. I'm not seeing why this is happening. Can anyone point me in the right direction?
Thanks Jack. When I look at the workflow, I see the status "Waiting For Support" has a transition of "Respond to Customer" which has a destination status of "Waiting for Customer". That transition has 5 Post Functions: 1. Set Issue Status to the linked status of the destination workslow step 2. Add a comment to an issue if one is entered 3. Update change history of an issue and store the issue in the database 4. Re-index an issue to keep indexes in sync 5. Fire a Generic Event that can be processed by the listeners. Steps 1 and 3 is where I would assume this is happening, but I can't edit either of those functions (I'm guessing because these were auto-generated?). Am I looking in the right spot?
Hi Atlassian Community! This is Teresa from the Atlassian team. My colleague Paul Buffington @Buff and I are excited to share a brand new ITSM resource we’ve created – "The Complete Guide to At...
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