I can see that in Automations you can create a condition to say when new requests are created then assign to an individual staff or auto assign but I wanted to assign to the agent that is replying, rather than having to press 'Assign to me' after having just replied... is there any way to achieve this?
I guess you are referring to a scenario where a customer comments on an issue and this comment would reassign the issue to the internal support agent.
A scenario like this would normally be handled through workflow transitions. If you ask the customer a question, you would normally also change the issue status to something like 'Waiting for Customer'. When the customer comments on the issue to answer the question, you would transition the issue back to a status like 'In progress' or 'Waiting for support'.
You have a specific automation rule for this: Transition on comment.
Assigning the issue can be done through post functions of your workflow. But if you handle this through status transitions, you don't even need to reassign. It is perfectly fine to keep the agent assigned to the issue while the status changes to 'Waiting for customer'. That way, he will receive a notification when the issue status changes again through the customer's comment.
We don't assign an agent to a new issue by default, it's usually replied to by whoever gets to it first... atm, when a staff replies to a new issue it still remains unassigned... I tried updating the Automation to say:
i.e. when comment is added by an agent and issue was Waiting for customer then edit assignee to a hardcoded agent - and that works ok... it's just that I want the assignee to be relative to the agent replying to the ticket rather than a static assignee.
That's exactly why your workflow might be a better option. If an agent does something with the ticket, it is a good idea to inform the customer of this fact, e.g by transitioning it from Open to In Progress. Within that transition, you could assign the issue to the CurrentUser(), which does this automatic assigning for you then.
A maybe more important side effect of this would be that your customer has a clear idea of the issue status.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Hi Atlassian Community! My name is Shana, and I’m on the Jira Software team. One of the many reasons this Community exists is to connect you to others on similar product journeys or with comparabl...
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