149
Customers have installed this add-on in at least 149 active instances.
    by Akeles Consultingfor JIRA Server 7.0.0 - 7.2.2 and more versions
    Versions available for JIRA Server 5.0 - 6.4.14
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Akeles Consulting supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Reassign your tasks automatically when you are away

    Reassign your tasks automatically when you are away

    Reassignment of issues by project

    Let people know that more time is required

    Reassign issue to your co-workers

    Specify rules to perform reassignment during your absence by project level as well as global level.

    If a message is specified in the rule, it will be added as a comment to the issue.

    Allow you to specify who to reassign to for various projects. Will not reassign if he is not around too.

    More details

    It will help to prevent untended issues and improve response time by reassigning it automatically based on rules for different projects.

    • It will help to improve customer service satisfaction with a comment to let them know more time is required.
    • It will let you enjoy your holidays with a peace of mind.

    With these features, you can use JIRA as your task management system.

    The addon is also known as

    • Abwesenheitsassistent (German)
    • Assistant d'absence (French)

    User reviews

    (6)
    Sign in to write a review »
    by CÉSAR CAAMAÑO BEIRO on 2014-04-23
    This plugin provides a very useful functionality in jira projects where the absence of a person is important for the issue resolution cycle. It is very easy to use and works fine in our Jira 6 instance. As the previous comment says in future versions it would be interesting an option to establish one rule for all projects.
    Was this review helpful?YesNo
    by Kamil Grabowski on 2014-01-20
    I would like to add some new feutures: * One rule for all the projects - I would like to add new rule for all projects, not only for one project. If i have 100 projects i must click 100 rules instead of one. * Sometimes i would like add my coverer to watchers list only. * Cascading coverer - if C is coverer for B and A is coverer for B then when someone assign to C tickets should be assgined to A (C -> B -> A). Plugin should discover loops (for example C -> B -> A -> C)
    Was this review helpful?YesNo

    Akeles Consulting

    Hi Kamil, Thanks for your suggestions. The initial design to have separate rules is because different projects might have different coverers and some projects do not require coverers. I have added 2 new feature requests to our tracker. For the cascading coverer, it might be better for C to know that B is also not around and then set A as a coverer. Maybe D will be a better candidate than B over A to cover C during his absence. The cascading select might just lead to undesired reassignment.

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more

    Support

    Akeles Consulting supports Out Of Office Assistant. You can visit the support site to get help.

    Get support

    Versions

    Version 1.5.2 JIRA Server 7.0.0 - 7.2.2 Released 2015-12-22

    Summary

    Support for Data Center and bug fixes

    Details

    • OOO-34 - To be compatible with Data Center
    • OOO-44 - Coverer cannot assign back to original assignee due to Change History ID
    • OOO-45 - NullPointerException when previous reassignment was from/to unassigned

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Out Of Office Assistant via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Out Of Office Assistant. You're prompted to log into MyAtlassian. Out Of Office Assistant begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Out Of Office Assistant versions compatible with your instance, you can look through our version history page.

    Similar add-ons