This is a complete guide on how to connect and sync your Elements and JIRA tickets. This guide covers permissions, installation, troubleshooting, and use-cases.

We often think of Elements.cloud as a one-stop solution for Org change management. For smaller teams, it can serve as a complete capture -> plan -> analyze -> execute suite.

However, when it comes to enterprise-level organizations, it is not going to replace dedicated project management tools .

We support connection with:

Following permissions are required to successfully connect Elements to JIRA:

You can connect:

You can map:

We recommend using Elements process maps to document how you work in the form of a UPN diagram.

Ask yourself why you want to use the integration, and what you need to get from it to benefit - what problems will it solve? Document your ideal process using the integration. Which teams are using it? Which issue types do you actually need in Elements, is it just the Epics and stories, or do you need other tasks and bugs too? Which projects do you need, if you use more than one?

Below are two main use-cases for integrating Elements and JIRA

We strongly recommend that you make Elements the application where your work items (business requirements and user stories) originate. Consult this use-case.

To set up a connection, go to "Space Settings" and select "Connections" in the left-hand menu.

Then choose the JIRA tab at the top and click "New connection" to create a new development project for JIRA.

Once the JIRA connection has been established, you need to configure how JIRA and Elements will work together. This requires picking the JIRA project and configuring user story mapping for fields and statuses.

Choose one of the projects to connect with.

You will be asked to confirm the choice and load project data. This step is required because each project can have a different configuration.

Then click 'Add issue type' and choose which issue type to integrate with either business requirements or user stories in Elements.
​

You will see a screen that will list Elements workflow statuses for either user story or business requirement and standard and custom fields. From the dropdown, choose JIRA statuses and JIRA fields you want to map to the Elements ones.

If the JIRA user credentials used to set up the development project belongs to the Jira administrator then after selecting the Jira project you can click "Register webhook" to set it up automatically in Jira.

You will see a green notification message informing you that the webhook was successfully registered, and it will continue to show it as long as the webhook is successfully enabled. If already registered you will not need to re-register.
​

Once the setup is complete, all you need to do is enable the project. You can enable/disable the project at any time you want.
​

Go to list of business requirements and user stories in Elements main menu. Depending on your setup, go to either requirements or stories tab.

Click 'Import' button in the top right corner of the screen. Chose 'Import from JIRA' from the dropdown.

In the window choose from which JIRA development project you wish to import the user stories from (if you have more than one JIRA project connected).

Then from the 2nd dropdown list, select which of the connected issue types you want to import:

From the last dropdown, choose which of the mapped statuses you wish to include in the import request. Only issues in those statuses will be imported.

Depending on the number of user stories being imported, this operation may take some time. A few thousand JIRA issues would take a couple of minutes to sync.

Once the operation is complete, you will receive a notification.

In the main menu, select 'Changes'. Then open either the business requirements or stories tab.

First, ensure that your record is assigned to a JIRA dev project.

Select the record you wish to send to JIRA. In the details tab, find the 'JIRA integration' field and press 'Send to JIRA' button.

Start by selecting the stories you want to send. You can do this by selecting the checkboxes on the left of the screen.

To send a story to Jira it must be associated with a connected Dev Project, and must not already have an existing story in Jira. Right click your selected stories to open the context panel and you will see the option to "Send all to Jira".

Once you select this option you will see a window summarising the stories you want to send.

In some circumstances you will be unable to send all your stories. For example, if this story is already connected and exists in Jira, or if you have not selected a Dev Project.

When you press confirm, all stories in the "Stories to send" tab will be sent to Jira, and those that cannot will be skipped.

You should see a notification when the operation is complete.

At any time, you can delete your development connection. Just click on the bin icon on the JIRA connections list in your Space's settings:

Deleting a JIRA connection is irreversible. This action does not delete any stories in either Elements or JIRA, but it removes all connection records between the two. To confirm, you must type the name of the project you wish to delete.