| Table of Contents |
|---|
In addition to outgoing communication via Outcoming WebHooks we also support incoming calls via our Rest API.
...
While creating a Token please pay attention to the expiration date. Suggest to use shorter timeframe of one off tokens to extract data or smth. If you plan to use Jira Automation Integration suggestion is to user longer living tokens.
...
Header: <Name: Authorization, Value: Bearer“Personalized Token Created on previous step”>
...
An example of outcoming integration is most probably executing build or running certain pipeline when version is moved to specific destination column. Such flexibility could be achieved via Outcoming WebHooks.
If you trigger builds/pipelines manually or with some other automation you might want to
...
move version in progress when at least one encompassing issue is in progress
move version to done when all issues are done, or update issues to done when version is moved to done (either independant or in scope of package)
mark all Epics as Released when versions/package is Released.
etc.
Same story here - use Outcoming WebHooks to run Automation in Jira as post action in Release management or use our Rest API to execute some actions in Release Management in scope of Jira Automation rule.
Find out more details in Jira Automation Integration section of this documentation.