Skip to main content

​
Intro

Jira Software is part of a suite of solutions meant to assist teams of all sizes in managing their workload. Jira was originally intended to be a bug and issue tracker. Jira, on the other hand, has matured into a strong task management application for all types of use cases, ranging from requirements and test case management to agile software development. The JIRA Writeback connector allows users to write Domo data back into JIRA records in order to create or amend them. You connect to your JIRA Cloud WriteBack account in the Data Center. This topic discusses the fields and menus that are specific to the JIRA Cloud connector user interface. General information for adding DataSets, setting update schedules, and editing DataSet information is discussed in Adding a DataSet Using a Connector.

Primary Use Cases

  • Tracking progress and movement of tickets

  • Number of tickets assigned to specific users or groups

  • Seeing if too many tickets of a certain type are open (bugs)

Primary Metrics

  • Bug / issue / ticket tracking (by age, type, status, submitter)

  • Completed tickets per team

  • Ticket resolution time

  • Project management metrics (tracking individual tasks of a larger project or epic).

Primary Company Roles

Product managers

Average Implementation Time

This can vary wildly depending on the implementation and the user’s level of knowledge of their JIRA system.

Ease of Use (on a 1-to-10 scale with 1 being easiest)

7

​
Best Practices

  • You should usually use Replace with the JIRA Cloud connector, as Append does not work well.
  • If the query is for data across a long time period, scheduling should be kept to a minimum (once a day). For shorter queries, more frequent updates are appropriate.

​
Prerequisites

To connect to your JIRA Cloud WriteBack account and create a DataSet, you must have:
  • The domain of your JIRA Cloud account
You can authenticate to the JIRA Cloud Write Back connector with the same credentials you use to log into your Jira account online.

​
Connecting to Your JIRA Cloud Write Back Account

This section enumerates the options in the Credentials and Details panes in the Jira Cloud Connector page. The components of the other panes in this page, Scheduling and Name & Describe Your DataSet, are universal across most connector types and are discussed in greater length in Adding a DataSet Using a Connector.

​
Credentials Pane

This pane contains fields for entering credentials to connect to your (third-party tool) account. The following table describes what is needed for each field:

Field

Description

Domain The domain of your JIRA Cloud account. Jira Server accounts are not supported for OAuth.
Once you have entered valid JIRA Cloud credentials, you can use the same account any time you go to create a new JIRA Cloud WriteBack DataSet. You can manage connector accounts in the Accounts tab in the Data Center. For more information about this tab, see Manage Connector/Adapter Accounts.

​
Details Pane

This pane contains a primary Reports menu, along with various other menus which may or may not appear depending on the report type you select. The following reports are available:

Report

Description

Create Or Update Issues
Update the Issue Update or change the issue in Jira.
Get the Issue Retrieves the list of issues.
Create Bulk Issues Create list of issues.
The maximum limit for creating bulk issues are 50.
Create Single Issue Create one issue at a time in Jira.
Add Comment Add comment to an issue.
Update Comment Update or change a comment to an issue.
Create Issue Link Create a link for an issue in Jira.
Search User Search for a specific user in Jira.
Create Or Update Project
Get Project Retrieve a project from Jira.
Create Project Create a project in Jira.
Update Project Update a project in Jira.

​
FAQ

You can use this connector to update your Jira issues or create new issues back to your source systems.
JIRA uses basic authentication and personal access token based on the user selection.
Data from Jira’s servers are usually made available to the API immediately.
This is not applicable for this connector.

​
Other Panes

For information about the remaining sections of the connector interface, including how to configure scheduling, retry, and update options, see Adding a DataSet Using a Connector.