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.
Tempo Integration
How do changes to Tempo plans affect connected Out of Office rules?
Changes to Tempo plans directly affect connected Out of Office rules: deleting a plan removes connected rules, changing dates modifies rule dates, and changing the internal issue updates the rules. If the internal issue is replaced by one not integrated with Out of Office Assistant, the connection breaks.
Further reading: Activating Out of Office rules from Tempo.
The integration of Tempo with Out of Office Assistant was working and now it’s not. What’s going on?
Tempo API Tokens have a maximum duration of 90 days. If your integration stops working, check if your API token has expired and issue a new one.
What happens to Out of Office rules when a plan with a duration of less than 8 hours is created in Tempo?
Out of Office rules reflect the exact time defined in updated plans with durations less than 8 hours. If a plan is for a part of the day, the rule will activate only during those hours.
Further reading: Activating Out of Office rules from Tempo.
What happens to Out of Office rules when a plan with a duration of more than 8 hours is created in Tempo?
For plans with durations of more than 8 hours, Out of Office rules will consider the entire date, including times outside typical business hours.
Further reading: Activating Out of Office rules from Tempo.
Does the Out of Office Assistant support stacking multiple plans in a single day?
Yes, but if there's a plan for any day with a duration of at least 8 hours, rules for the entire day will be generated, ignoring other plans for that day.
Further reading: Activating Out of Office rules from Tempo.
What permissions do I need to integrate Out of Office Assistant with Tempo Timesheets?
An administrator must set up the connection and select eligible internal issues to trigger rules.
Further reading: Tempo Integration - Admin Setup.
Can individual users configure their own Out of Office plans in Tempo?
After admin setup, users can map available internal issues to their Out of Office templates.
Further reading: Tempo Integration - User Setup.
For a shared configuration option, please raise a ticket here with the summary “Tempo shared templates”.
My team doesn’t have access to the integration with Out of Office but the admin already created the connection. What’s going on?
For the integration to work, all relevant users must be included in a single team in Tempo. Users outside this team will not have access to internal issues for Out of Office Assistant.
Further reading: Tempo Integration - Admin Setup.
Are Out of Office Assistant templates shared between users or individual?
Templates are currently individual to each user. Shared templates are planned for a future release.
Feature request: For shared template configuration, please raise a ticket here with the summary “Tempo shared templates”.
How does a JIRA admin select the internal issues that can trigger Out of Office rules?
Admins must select internal issues during setup, with the app suggesting a list of every internal issue defined in Tempo.
Further reading: Tempo Integration - Admin Setup.
Will users outside of the designated team in Tempo have access to Out of Office rules?
Users outside the designated team in Tempo will not have access to internal issues for the Out of Office Assistant.
How do I link Out of Office Templates with Tempo plans?
Linking templates with Tempo plans involves accessing the Out of Office Assistant App in Jira, navigating to the "integrations tab," and clicking on “Configure” next to the Tempo row.
Further reading: Connecting Out Of Office Templates With Tempo Plans.
Can multiple Out of Office rules be activated from a single Tempo plan?
Yes, any number of Out of Office rules can be activated based on Tempo plans by mapping the corresponding template to internal issues.
Further reading: Connecting Out Of Office Templates With Tempo Plans.
Are there any specific settings I need to enable in Tempo to use it with the Out of Office Assistant?
Before integrating, ensure you have a Tempo team including all relevant users, at least one user with plan modification rights, and at least one internal issue for non-billable time.
Further reading: Integration with Tempo.
Do Out of Office rules update in real-time when changes are made to Tempo plans?
Updates from Tempo plans to Out of Office rules may take a few minutes, but a refresh button in Out of Office Assistant can sync changes immediately.
How can I verify that the integration between Tempo and Out of Office Assistant has been set up correctly?
To test the integration, check if connected plans generate Out of Office rules with the same dates and duration as the plan. Make sure all prerequisites are met.
Further reading: Integration with Tempo.
Can the integration be customized to trigger Out of Office rules for specific project roles within Tempo?
Currently, specific roles or permissions in Tempo are not considered for the integration.
Feature request: For customization based on roles, please raise a ticket here with the summary “Tempo roles”.
Is it possible to disable the Out of Office Assistant from activating rules based on certain Tempo plans?
To prevent rule activation from Tempo plans, users need to remove or modify templates mapped to the internal issues.
How does the app handle conflicting Tempo plans for a single user?
Out of Office respects overlapping plans in the order they are created. Later plans will only go into effect for durations that don't conflict with older rules.
Can users override Out of Office rules set up through Tempo Integration?
Rules generated from Tempo are read-only in Out of Office, but they can be overridden by changing the template configuration or modifying the originating plan in Tempo.
Are Tempo plan approvals required before triggering an Out of Office rule?
No, approvals are not currently factored into the integration with Tempo.
Feature request: To request this feature, please raise a ticket here with the summary “Tempo approvals”.
How does the integration manage public holidays as defined in Tempo?
Public holidays in Tempo are not currently considered in the integration.
Feature request: To request this feature, please raise a ticket here with the summary “Tempo bank holidays”.
Does the app support all types of Tempo time-off plans (paid, unpaid, sick leave, etc.) when integrating?
Yes, the app supports all types of time-off plans as long as they are mapped to Out of Office by an admin.
Further reading: Integration with Tempo - Admin Setup.
Can Tempo Integration be configured at a project level or only instance-wide?
Tempo integration is typically configured at a team level, which can effectively serve as instance-wide access.
Further reading: Integration with Tempo - Admin Setup.
Can Out of Office statuses from the app be fed back into Tempo for resource planning?
Currently, there is no feedback loop from Out of Office statuses back into Tempo. Feedback on this feature can be provided to both Tempo and Out of Office Assistant support teams.