Documentation Index
Fetch the complete documentation index at: https://domoinc-jkreitzman-patch-1.mintlify.app/llms.txt
Use this file to discover all available pages before exploring further.
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 enables 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 Replacewith the JIRA Cloud connector, as Appenddoes 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
Connecting to Your JIRA Cloud Writeback 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. |
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 |
| ||||||||||||||||
| Create Or Update Project |
|
FAQ
What can I do with this connector?
What can I do with this connector?
You can use this connector to update your Jira issues or create new issues back to your source systems.
What is the authentication method for this connector?
What is the authentication method for this connector?
JIRA uses basic authentication and personal access token based on the user selection.
How frequently will my data update?
How frequently will my data update?
Data from Jira’s servers are usually made available to the API immediately.
Is there a support for paging for this connector?
Is there a support for paging for this connector?
This is not applicable for this connector.