In the JIRA Service Desk, I am trying to define a workflow for a customer incident. However all the actions/steps seem to be driven only from our side and not from customer side.
For example, when a solution is provided to the customer, only customer should be able to confirm the solution or re-open it. But i could not able to find any such option. Re-open option is available for an agent but it should be available at customer's side.
How can I define a workflow for incident management, where I can mark or assign certain steps to customer as Responsible?
Do let me know in case you need further information from my side.
@Rinju Mukherjee, for the reopen piece you can expose a link on the for this purpose. On the reopen transition in the workflow editor you can expose to the portal. For the customer confirmation piece you can replicate the default automation where the agent can respond to customer moving the issue to the Waiting for Customer and when they reply it moves back to Waiting for support. For example, you could create a new status called "Customer Approval" with a transtion of "Request Approval" and an automation rule that would have a canned comment "Your issue has been resolved. Please review the solution and let us know if we can proceed with closing." The automation rule would be similar to the one for Waiting for Support <--> Waiting Customer.
Let me know if this does not make sense or is not what you are looking for.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs