Jira Automation Round Robin Assignment Vacations

[Rosa M Fossi]

I know that I can round-robin assign tickets to a group / role / list of users, but how do I account for vacations / out-of-office users?   

I don't have the bandwidth to update every single automation when someone is out sick or on vacation.  Or update their group / role membership for that matter.  :( 

[Jaime Capitel (resolution)]

Apologies for necroposting, but perhaps someone arrives here with the same problem. 

My company has an app that solves that exact problem: Out of Office Assistant for Jira.

Here's a guide to combining a round robin automation rule to a group member with Out of Office:

https://wiki.resolution.de/doc/out-of-office/user-guide/skip-absent-group-members-in-a-round-robin-automation

[Florian]

Hi Rosa,

I think there is no automation possible right know. First of all Jira does not know who is available and who is not. And even if you find a way to fiddle it into the user account, there still is no way to make Jira getting some sense out of this information. 

As of now I don’t know any plugin on the marketplace that can do the job.

The best thing you can do is to hand in a feature request and be patient.

If this critical for you then your company can look for an Atlassian Partner to implement this feature for you. https://partnerdirectory.atlassian.com  But I think this will cost a few bucks. 

[Florian]

Hi Rosa, 

i found my first answer too disappointing. So I searched a bit and found this

 https://marketplace.atlassian.com/apps/1221345/a4j-absence-for-jira?hosting=server&tab=overview

I can’t tell anything about it. But you can ask you admin to give it a try. 

[Rosa M Fossi]

Thanks so much for your response.  While searching the community I've ran into much of the same disappointment...   I'm the JIRA Genie at my company and would be willing to implement an addon, but the ones I've ran into so far are all for Server (we're on a cloud instance). 

I never thought of possibly reaching out to an Atlassian Partner. Thanks for the suggestion... although I doubt this issue is a problem enough for leadership to dedicate any $$$ to it.