Creating workflows for Jira Cloud users

Let Oomnitza be your single source of truth!

You'll get visibility of your users as data from Jira is automatically transformed into consumable information and actionable insights.

Connect Oomnitza and Jira in minutes

You'll get visibility of your Jira users by creating configurable workflows to automate tasks such as:

• • Retrieving detailed user information
  • Onboarding and offboarding users
  • Managing Jira ticketing in Oomnitza

Contents

1. Before you start
2. Create user workflows

Before you start

Before you can create workflows with Oomnitza, you'll need to have added your Jira credentials to Oomnitza.

We recommend that you also set the Jira Cloud ID, Subdomain, and Issue Type as global variables.

Create user workflows

To create a user workflow, you must complete these steps:  

1. Click Configuration > Workflows 
2. Click Add  and select Users from the Objects list.
3. Edit the Begin Block and add rules to trigger the workflow. For example, if you set the Actions to Schedule and add a rule so that the Email Equals <EmployeeEmail> you can trigger a workflow to fetch a user matching a certain name on a specific date. Refer to Using the Begin block. 
4. Drag and drop the API block onto the Sandbox.
5. Click Edit on the API block and enter Jira in the search field. 
6. Select a preset from the list below. To choose a preset, click the forward arrow (>).
   
   • Add Comment to issue (Basic auth)
   • Change Issue Status with Comment (Basic auth)
   • Create Issue (Basic auth)
   • Create User (Basic auth)
   • Delete User (Basic and OAuth)
   • Get User (OAuth)
7. Select the credentials that you created in Adding your credentials.
8. Your global variables can be configured by following the steps in Adding Jira global variables.
   
9. Enter any mandatory information when prompted.
10. Select Advanced Mode.
11. Select the Response tab. You can map the entire response by placing {{response}} in the Response field and mapping it to a custom long text Oomnitza field, such as API Response. Once you have the entire response, you can then parse the JSON response values to custom Oomnitza fields, as per the example below.
12. Connect the Blocks. 
13. Save, validate, and activate your workflow.

Reference articles for workflows

• Mapping positive and negative responses
• Troubleshooting workflows 
• Using the API block

Using the Jira Add Comment to Issue preset

The Jira Add Comment to Issue preset adds a comment to a Jira issue. When you select this preset, you need to supply a Comment.

The ticket to be updated is referenced in the Advanced Mode > Information tab in the property{{WFVariables.jira_ticketno}}.For information on how to create workflow variables refer to Creating a Workflow variable.

See Jira API Documentation: Add comment.

Using the Jira Change Issue Status with Comment preset

The Jira Change Issue Status with Comment preset adds a comment to a Jira issue and performs an issue transition (for example, transitioning an issue from To do to Closed). When you select this preset you need to supply the following information:

• Comment - the comment you want to add to your Jira ticket. 
• Transition ID - The ID or key of the issue you want to move to. For example, if you wish to move your ticket from In Progress to Done you will need to find the ID of Done. You can find the ID within your Jira instance by going to Settings>Issues >Workflows>View. You will see the ID in brackets next to the transition name, for example, Done(5).

The ticket to be updated is referenced in the Advanced Mode > Information tab in the property{{WFVariables.jira_ticketno}}.For information on how to create workflow variables refer to Creating a Workflow variable.

See Jira API documentation: Transition issue.

Using the Jira Create Issue preset

The Jira Create Issue preset creates an issue within your Jira instance. When you select this preset you need to supply the following information:

• Project Key - The Project Key is the prefix of the issue number. In the example of JRA-123, the JRA portion of the issue number is the Project Key. This value is case-sensitive.
• Issue Summary - A summary of the issue.
• Issue Description - A description of the issue. 
• Issue Type - Your Issue Type should be derived from the variable you set in Adding Jira global variables. Typical values include Bug, Task, Sub-task, Story. The value depends on the configuration of your Jira instance and should be validated there. These values are case-sensitive.

Important
To avoid a 400 error, ensure that you use the correct case for both the Project Key and Issue type. Using the incorrect case will result in a failed request.

Did you know?
You can add more information to the message body in the Advanced Mode > Body tab.

For additional information, refer to the Jira API documentation: Create issue.

Using the Jira Create User preset 

The Jira Create User preset creates a new user in your Jira instance.

The user to be updated is referenced in the Advanced Mode > Body tab in the following properties: {{email}}, {{full_name}}, {{username}}.

For additional information, refer to the Jira API documentation: Create user.

Using the Jira Delete User preset 

The Jira Delete User preset deletes a Jira user.

The user to be deleted is referenced in the Advanced Mode > Information tab in the property{{jira_user_id}}.

For further information refer to the Jira API documentation: Delete user.

Warning
If successful, this workflow returns a204 No Contentresponse code. Do not map a response in Advanced Mode > Response, as it will cause the content to fail due to no content.

Using the Jira Get User preset 

The Jira Get User preset gets a Jira user.

The user to be retrieved is referenced in the Advanced Mode > Information tab in the property{{jira_user_id}}.

Note
This API requires the read:jira-userscope. For additional information, refer to the Jira API documentation: Get user.

Reference articles for workflows

• Mapping positive and negative responses
• Troubleshooting workflows 
• Using the API block