Important Update Effective February 1, 2024!
Due to recent changes in Jira and Confluence, we've made the tough decision to discontinue the OpenID Connect (OIDC)/OAuth app and no longer provide new versions for the newest Jira/Confluence releases as of January 31, 2024.
This is due to some necessary components no longer shipping with Jira/Confluence, which would require some extensive rewrites of the OIDC App.
Important Update! This app will be discontinued soon!
Due to recent changes in Jira, which no longer ships with some components required for our Read Receipts app to run, we've made the tough decision to discontinue the app, as of Februar 5, 2025.
Important Update! This app will be discontinued soon!
We've made the tough business decision to discontinue the app, as of January 11, 2025.
Integration with Tempo - User Setup
Connecting Out of Office Templates with Tempo Plans
This guide shows how a user can configure the connection between Tempo and Out of Office Assistant.
Goal
Once configured, users can plan time off in Tempo plans and automatically activate any number of Out of Office rules.
Prerequisites:
- An Admin has connected Tempo with Out of Office Assistant for Jira Cloud
- An Admin has defined which internal issues are being used in Tempo for planning PTO (sick days, vacation, trainings, parental leave, etc.).
Guide
1. Access the Tempo Configuration
- Click on the Integrations tab. (If you have no active rules, you will see the Integrations tab in the rules screen.)
- On the Tempo row, you should see an icon saying "Connected"
- Click on Configure button next to it.
2. Understanding the Configuration Page
When you land on the Configuration page of the Tempo Integration with Out of Office Assistant, you will see:
- A link to every available template. In the current version, templates cannot be shared among users. This means that the list of all templates will be initially empty.
- A list of available internal issues. These are the types of time off that you can use in Tempo, as setup by your admin. To define what should happen when you plan time off with each of them, you need to start mapping Out of Office templates.
2. Start adding templates
Click on one of the blue "Add Template" buttons next to each Tempo internal issue.
3. Click on Add new template
This modal will later show every template that you have created. Here, you can:
- Select an existing template from the table
- or add a new template
4. Fill in the details of the template
If you create a new template, you will have to fill in the details. Follow the instructions in the User Walkthrough if you don't know how to do this.
Templates are very similar to Out of Office rules, with two differences:
Templates have names.
Templates don't have start and end dates, since this information is received from the Tempo Plans.
When you create a template, Out of Office will make sure that there are no duplicates. In particular:
- Make sure that the name you have entered is unique.
- Make sure that you don't repeat the combination of projects/JQL filter, Coverers, Coverer for Approvals, and Message
5. Save the rule template
Once you have filled in the details, you can save the template. This will automatically add the template to the internal issue.
The exception is that the template will not be added if the issue is already mapped to a template with the same scope.
Once the template has been added, you will be able to see it in the overview.
7. Add additional templates
Once your first template has been added, you can keep mapping templates to issues.
This is a many to many relationship, so you can:
Add multiple templates to an internal issue
As long as they have different scopes, you can add as many templates to a single internal issue as you desire.
Please note the scope limitations, though:
It's only possible to have one template that applies to All Projects per each internal issue;
It's only possible to have one template that applies to a same project per each internal issue;
It's not possible to have two templates with the same JQL under the same internal issue. However, the app doesn't evaluate whether different JQLs under an internal issue overlap. For that reason, we recommend being very careful with the use of multiple JQL rules.
When you try to add an existing template to an internal issue that already has a mapped template, the modal only allows to select compatible templates:
Add the same template to multiple internal issues.
It's perfectly possible to use a single template and apply it everywhere. For example, a user may decide to use the app to delegate their tasks to the same coverer(s). They will then simply add the same All Projects template to every internal issue, like in the example above.
8. Checking all Tempo Templates
To see every template, click on the link with the eye button
In this table, you can see every detail of every template, and make changes:
- Add Templates.
Edit templates.
Delete templates. Templates can only be deleted if they are not in use.