Skip to main content
Skip table of contents

Post Function to check the existing assignee is out of office

This feature is available from version 4.1.0 onwards

Background

Out Of Office Assistant will check for OOO whenever the issue has a new assignee or the current assignee is mentioned.
If there is no change of assignee, it does not perform reassignment even if there is status change or a new comment.

This default behaviour is designed so as some users may not want to reassign to the coverer for their existing issues that they may be working on.
Moreover, the user should be able to reassign the existing issues to a coverer if necessary.

However for some urgent use cases such as a helpdesk, it may be necessary to reassign the ticket to the coverer when the existing assignee is out of office.

Solution

It is possible to add a new post function “Check for OOO upon transition” to run OOO checks on the existing assignee.

The post function will check if the current assignee is Out of Office after the issue is transitioned.
If the current assignee is Out of Office, apply the relevant Out of Office rule.

Prerequisites

You will need to be a Jira administrator to be able to add post functions to a workflow.

Steps

  1. Edit the workflow associated with the project and issue type

  2. Edit the workflow transition that you want to enforce the OOO checks

  3. Click on the Post Functions tab

    Workflow post function (Before).png

  4. Click on Add post function link

  5. Select the Check for OOO upon transition post function

    Check for OOO upon transition post function.png

  6. Click the Add button to save the change

  7. The new post function will be added to the workflow transition

    Workflow post function (After).png
  8. Publish the workflow

  9. Now, whenever any issue associated with the workflow go through the selected transition, Out Of Office Assistant will perform a check for the final assignee of the issue and execute any rules that belong to that user if they are OOO.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.