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.
The Out of Office Assistant REST API
In your Out of Office rules list you may find a button to create a rest API token.
If not, please ask your Jira Cloud administrator to either issue a token for you or to switch on the possibility for users to create their own tokens.
With this token you can either
- use the Rest API of the app in a normal way, see Out of Office Assistant Rest API | resolution-cloud | SwaggerHub for information how to use it,
- use our Zapier integration by using following link: https://zapier.com/developer/public-invite/159108/45f85ccf3e0817570f19f9bd8f95ca78/
- Use our Slack integration with the Slack button that will show when you create a new API Token.
What's possible with the Out of Office REST API
The REST API allows to:
- read existing Out of Office rules to send that information to other systems
- Modify or create new Out of Office rules from third party systems
As an example, you could integrate Outlook with Out of Office Assistant to create new absences whenever you add a vacation event, or a training. However, we recommend implementing the integration with Outlook via Zapier, as this is a no code approach that works really well already.
There are two different scopes for the API Tokens:
- Regular users can access and modify information about their own rules
- Admins can access and modify rules for any users in the instance.
For more details, refer to the documentation.
Important details
Please note:
Rules created via the API can be changed manually by users
While the REST API can change and delete rules coming from an external connection (like Outlook or Tempo), these changes will have no effect, since the rules will be synced again within 15 minutes
The REST API cannot currently be used to create templates. Please reach out to our support if this is something that you would like to do.
By default, rules created via the API will show with the source name REST API. However, this can be changed and take any value. Just name your connection with the parameter “trigger name”. This can help your users understand when the source of an absence is, for example, their mandated HR system.