Many organizations working with Agile or Scrum are already familiar with Jira as a tool to manage and track team tasks. But did you know that Jira can also be automated to save time and improve efficiency? By using Jira API together with Webhook, you can cut down on manual work and speed things up significantly.
Today, Khun Praew from the Platform Services team will share a simple example of how Jira Automation works, along with its key benefits and limitations, all in just one minute.
What is Jira API?
Jira API allows you to control Jira directly through programming. Examples include:
1. Reading card information: /rest/api/3/issue/{issueIdOrKey}
2. Adding a comment to a card: /rest/api/3/issue/{issueIdOrKey}/comment
3. Changing the card’s status: /rest/api/3/issue/{issueIdOrKey}/transitions
What is Jira Webhook?
A Webhook is a mechanism that sends Jira data to another app or web application whenever a defined event or condition occurs.
Real-world use case
Normally, requesting access to Git requires multiple manual steps. The Project Owner has to manually grant access by adding names and details, which takes time and effort. But with Jira Automation integrated with Jenkins, all those manual steps are reduced to just a few clicks. On top of that, the entire process can be tracked and monitored easily through a Jira Dashboard.
Example Flow with Jira Automation
1. A user creates a Jira card and fills in required details such as Git ID, project, and role.
2. The Project Owner simply reviews and approves.
3. Once the status is set to Approved, a webhook automatically triggers Jenkins, which is pre-coded to grant the user Git access for the project.
4. After Jenkins completes the job, the result is updated back to Jira, where the user can check the status instantly.
Key Benefits
1. Save time by reducing repetitive tasks.
2. Minimize human error and resource usage through automation.
3. Track access requests in one place via Jira Dashboard.
Limitations
1. Conditions in the webhook must be carefully written to avoid false positives or negatives.
2. Human review is still required for approval steps.
Looking for a DevOps solution that automates your workflow and reduces business costs? SCB TechX helps you modernize your delivery pipeline and bring high-quality products to market faster, building a foundation for long-term growth.
For service inquiries, please contact us at https://bit.ly/4etA8Ym
Learn more: https://bit.ly/3H7W9zm
Ref:
https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about
https://www.atlassian.com/software/jira
https://developer.atlassian.com/server/jira/platform/webhooks/
