Workflow
Atlassian Jira - Modular Automations
Overview
The integration of Itential and the Atlassian Jira solution enables network teams to utilize its REST API to build automations that can include common tasks for Jira issue management. This is a library of related automations that can be used as modular components in your own larger, end-to-end workflows.
Workflows
Name | Overview |
---|---|
Create Issue - Jira - REST | Create an issue in Jira |
Create Project - Jira - REST | Create a project in Jira |
Transition Issue - Jira - REST | Transition an issue in Jira to a different status |
For further technical details on how to install and use this Workflow Project, please click the Technical Documentation tab.
Table of Contents
Getting Started
This section is helpful for deployments as it provides you with pertinent information on prerequisites and properties.
Helpful Background Information
Workflows often include logic that varies from business to business. As a result, we often find that our Workflow Projects are more useful as modular components that can be incorporated into a larger process. In addition, they often can add value as a learning tool on how we integrate with other systems and how we do things within the Itential Automation Platform.
While these can be utilized, you may find more value in using them as a starting point to build around.
Prerequisites
Itential Workflow Projects are built and tested on particular versions of IAP. In addition, Workflow Projects are often dependent on external systems and as such, these Workflow Projects will have dependencies on these other systems. This version of Atlassian - Jira - REST has been tested with:
- IAP 2023.2
External Dependencies
Name | OS Version | API Version |
---|---|---|
Jira | v3 |
Adapters
Name | Version | Configuration Notes |
---|---|---|
adapter-jira | 2.3.1 |
How to Install
To install the Workflow Project:
- Verify you are running a supported version of the Itential Automation Platform (IAP) as listed above in the Supported IAP Versions section in order to install the Example Project.
- Import the Example Project in Admin Essentials.
Testing
Cypress is generally used to test all Itential Example Projects. While Cypress is an opensource tool, at Itential we have internal libraries that have been built around Cypress to allow us to test with a deployed IAP.
When certifying our Example Projects for a release of IAP we run these tests against the particular version of IAP and create a release branch in GitLab. If you do not see the Example Project available in your version of IAP please contact Itential.
While Itential tests this Example Project and its capabilities, it is often the case the customer environments offer their own unique circumstances. Therefore, it is our recommendation that you deploy this Example Project into a development/testing environment in which you can test the Example Project.
Using this Workflow Project
Workflow Projects contain 1 or more workflows. Each of these workflows have different inputs and outputs.
Create Issue - Jira - REST
Create an issue in Jira
Capabilities include:
- Create an issue in Jira
Entry Point IAP Component
The primary IAP component to run Create Issue - Jira - REST is listed below:
IAP Component Name | IAP Component Type | Create Issue - Jira - REST | Workflow |
---|
Inputs
The following table lists the inputs for Create Issue - Jira - REST:
Name | Type | Required | Description | Example Value |
---|---|---|---|---|
adapterId | string | yes | Jira adapter instance name configured in IAP | Jira |
projectKey | string | yes | Project key where the issue needs to be created | ADAPT |
description | string | yes | Description of the new issue | Bug in the new release |
summary | string | yes | Summary of the new issue | Application crashes on passing empty id |
issueType | string | yes | Type of the new issue | Bug |
priority | string | yes | Priority level of the new issue | High |
label | string | yes | Label for the new issue | Hot |
Outputs
The following table lists the outputs for Create Issue - Jira - REST:
Name | Type | Description | Example Value |
---|---|---|---|
createdIssue | object | Result has a key response which contains id, key and url to the newly created issue | {
"id": "5600",
"key": "ADAPT-3240",
"self": "https://itential.atlassian.net/rest/api/2/issue/5600"
} |
Query Output
The following items show how to query successful results from the output of Create Issue - Jira - REST:
id
createdIssue.response.id
key
createdIssue.response.key
self
createdIssue.response.self
Example Inputs and Outputs
Example 1
Input:
{ "adapterId": "Jira", "projectKey": "ADAPT", "description": "Bug in the new release", "summary": "Application crashes on passing empty id", "issueType": "Bug", "priority": "High", "label": "Hot" }
Output:
{ "id": "265600", "key": "ADAPT-3240", "self": "https://itential.atlassian.net/rest/api/2/issue/265600" }
API Links
API Name | API Documentation Link | API Link Visibility |
---|---|---|
Jira REST API v3 Reference | https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about | Public |
Create Project - Jira - REST
Create a project in Jira
Capabilities include:
- Create a project in Jira
Entry Point IAP Component
The primary IAP component to run Create Project - Jira - REST is listed below:
IAP Component Name | IAP Component Type | Create Project - Jira - REST | Workflow |
---|
Inputs
The following table lists the inputs for Create Project - Jira - REST:
Name | Type | Required | Description | Example Value |
---|---|---|---|---|
adapterId | string | yes | Jira adapter instance name configured in IAP | Jira |
name | string | yes | Name of the new project | DEMO |
projectType | string | yes | Type of the new project | software |
projectTemplateKey | string | yes | Key of the template that will be applied to the new project | com.pyxis.greenhopper.jira:gh-simplified-agility-kanban |
abbreviatedName | string | yes | Abbreviated name of the project | DEMO |
description | string | yes | Description for the new project | A project for software demo team |
leadAccountId | string | yes | Account id of the project lead | 3112 |
assigneeType | string | yes | Default assignee for the new project | PROJECT_LEAD |
Outputs
The following table lists the outputs for Create Project - Jira - REST:
Name | Type | Description | Example Value |
---|---|---|---|
result | object | Result has a key response which contains id, key and url to the newly created issue | {
"id": 32184,
"key": "incident",
"self": "https://MmvAESOynfzkMznAoRy9-mhyD"
} |
Query Output
The following items show how to query successful results from the output of Create Project - Jira - REST:
id
result.response.id
key
result.response.key
self
result.response.self
Example Inputs and Outputs
Example 1
Input:
{ "adapterId": "Jira", "name": "DEMO", "projectType": "software", "projectTemplateKey": "com.pyxis.greenhopper.jira:gh-simplified-agility-kanban", "abbreviatedName": "DEMO", "description": "Project for software demo team", "leadAccountId": "3112", "assigneeType": "PROJECT_LEAD" }
Output:
{ "id": 32184, "key": "incident", "self": "https://MmvAESOynfzkMznAoRy9-mhyD" }
API Links
API Name | API Documentation Link | API Link Visibility |
---|---|---|
Jira REST API v3 Reference | https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about | Public |
Transition Issue - Jira - REST
Transition an issue in Jira to a different status
Capabilities include:
- Transition an issue in Jira to a different status
Entry Point IAP Component
The primary IAP component to run Transition Issue - Jira - REST is listed below:
IAP Component Name | IAP Component Type | Transition Issue - Jira - REST | Workflow |
---|
Inputs
The following table lists the inputs for Transition Issue - Jira - REST:
Name | Type | Required | Description | Example Value |
---|---|---|---|---|
adapterId | string | yes | Jira adapter instance name configured in IAP | Jira |
issueIdOrKey | string | yes | Id or key of the issue that needs to be transitioned | 265416 |
transitionStatus | string | yes | New status of the issue | Selected for Development |
Outputs
The following table lists the outputs for Transition Issue - Jira - REST:
Name | Type | Description | Example Value |
---|---|---|---|
result | object | Result has a key response which is empty if the transition was succesful | " " |
Query Output
There are no query output examples for Transition Issue - Jira - REST.
Example Inputs and Outputs
Example 1
Input:
{ "adapterId": "Jira", "issueIdOrKey": "265416", "transitionStatus": "Selected for Development" }
Output:
" "
API Links
API Name | API Documentation Link | API Link Visibility |
---|---|---|
Jira REST API v3 Reference | https://developer.atlassian.com/cloud/jira/platform/rest/v3/intro/#about | Public |
Additional Information
Support
Please use your Itential Customer Success account if you need support when using this Workflow Project.