Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Please share your experience with managing agents' vacations Edited

Greeting, I'm looking for ideas on how to handle vacation/sick leave days for my JSM agents.

I have ~18 JSM projects and 7 agents, I saw some apps in a marketplace, but always want to explore first solutions based on core functionalities.

The first that came to my mind is to create automation in each project paired with the Bulk change to catch all comments:

  1. If someone created an issue for a Person1 - re-assign it to Person2. ON/OFF that rule and edit Person2's name every time someone going on vacation.
    Simply change Project Lead as it's a default assignee. I can add any agent since they all are part of the Group which is added in the project's people.
  2. Create a filter, to Bulk change assignee in all Person1's issues to Person2 (I can re-do the action later thanks to the project IDs). This is needed if the Client will re-open the old request or add a new comment. 

How you guys solve this?


1 answer

0 votes

Hi @Alexey 

In our projects we also create an automation rule to change the assignee if there's a response/update on a ticket by the customer for the specific assignee that's on holidays. This works fine for us.

We don't have default assignees on create, but work with status intended for people to pick up unassigned tasks. So for the creation, we don't need anything additionally.

Kind regards

I see, well, since we have 1 project = 1 client = 1 agent scenario, we use Automatic assignee, so fewer automation rules needed.

So you don't re-assign ongoing tasks to the new agent, just keep him informed via automation about any updates where the assigned person who left on vacation?

Thanks for sharing that info!

Like Jorden Van Bogaert likes this

We do re-assign, but only when there's a customer response on the ticket during the absence of the agent. So the automation rule will be triggered when a customer posts a comment or when another update happens on the ticket (such as escalation, etc.)

I do understand that the use case is a little different when all tickets are auto-assigned to agents of course. I'm not immediately sure what the best approach would be in that case. You could simply create an agent queue and make someone follow up on the queue that contains active tickets of agents that are away and make the other agents decide whether they re-assign it to themselves or not.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Jira Service Management

ThinkTilt is joining the Atlassian Family!

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...

405 views 19 23
Read article

Community Events

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

Events near you