Step-by-step process of connecting the Jira integration in Elate.
Connecting Jira to Elate
Connecting your Elate account to Jira is incredibly simple and can be done in less than five minutes.
In Elate, click the arrow next to your name at the bottom-left corner of your screen. Select "Integrations" from the pop-out menu.
Click "Connect" on the Jira card under "Available".
3. Select whether you or someone else will be owning this Hubspot connection. If you have a Hubspot account with the proper permissions, this will be you! Select "Me".
4. This will pop open the connect flow. Follow the detailed step-by-step instructions provided in the flow to successfully connect to Jira.
5. Once connected, Jira will appear under the "Connected" tab.
Please note that it may take a while for your connection to fully sync.
Once you've accepted access, you will see the Jira plugin on your plugins page.
6. If you do not have a Jira account, or if you would like another team member to manage this Integration for your Elate Instance, select "Another Elate User" instead.
7. Use the drop-down menu to invite another user to connect Jira to your Elate account.
8. This user will receive an email invitation from Elate, asking them to login and connect to Jira. By selecting "Connect Plugin", your teammate will be automatically directed to the connect flow.
9. If you did not set up the connection, you will still be able to see who connected the Integration for your organization, pictured below.
Congrats - Your Jira account is now connected in Elate!
Now that you've connected Jira, you're able to connect to an outcome!
Managing Your Jira Integration
Once your Jira Integration is connected, the Integration Owner (the user who made the initial Integration connection) is able to "Manage" the Integration (see below).
This involves assigning other Elate members to the Integration, syncing, reconnecting, and disconnecting the connection.
Assigning Others to an Integration
If you are the integration owner and want to assign another team member to an Integration, go to your "Connected" tab on the Integrations page and select "Manage" on the Integration card.
From there, you'll be prompted to assign Integration access to another teammate. Find your teammate in the drop down and select "Assign to Integration".
Once invited, your teammate will appear in the drop-down.
To revoke Integration access, use the three-dot menu.
Syncing, Reconnecting, and Uninstalling Your Integration
As the Integration Owner, you can use the three-dot menu to Sync, Reconnect, and Uninstall your Integration.
While Integrations with Elate sync very frequently, there may be times when a manual sync is necessary. Choose sync to trigger this process.
Connecting Jira to an Outcome
Now that you have your plugin set up, navigate to an outcome to connect it to Jira. Select the 3 dot menu in the top right corner and select Connect.
*In this example, we will be walking through how to show total tickets on an Epic and percentage complete of an epic.
You will then be prompted to select the plugin you wish to connect. Select the Jira button.
You will then be taken to a screen to configure your outcome. Select the cadence you wish to view your outcome on the left hand side. Since we're pulling percent complete of an epic, we recommend setting the cadence to annual or quarterly so you're able to see the whole picture of how many tickets are in each status.
On the right hand side, this is where you will be able to configure the information being pulled over.
The resource we are pulling data from can only be Issues so that is the only option in the dropdown. We will narrow the issues down using the JQL link at the bottom.
The time field the data will be based on is going to be dependent on the time fields you use. In this example, we're using actual start to determine when the issue is getting pulled in. Another common time field to use is Created or Actual End. Please note the time field must be a description field on your Jira tickets, not a context field.
The group by field is going to be what shows us how complete our epic is or how many tickets are To Do, In Progress, Done, etc. In this dropdown, select the Jira: Status option to group.
The field you want to use from the resource is going to be how we're counting each ticket. In this example, we're using Summary because that is the title of the Jira tickets. You are also able to use the same time field you used in the above field.
The functions we're using here is Count. We want to count how many tickets are on the ticket total. Count is the most common function to use when connecting Jira.
The JQL link mentioned above will go in the box at the bottom below "What search should we apple when fetching this data?". This is where we are telling Jira what we want to pull in. The link in my example is: project = "KAN" and parent = KAN-5. I am looking at the KAN project board, where the Parent issue is KAN-5 (this is my epic, all child issues to the epic will have the parent link matching this). Check out Jira's JQL guide for more information on how to find and use the JQL function!
Once you're happy with the configuration, select the blue Save button.
Your outcome should then be populated based on the configuration of your outcome.
The outcome now shows that I have 5 total tickets on my epic and is color coded based on the status of the tickets. If you hover your mouse over the bar you'll be able to see the status breakdown and the percentage complete for your epic. In the example below, the epic is 40% done.
Connecting Jira to a Tactic
Great news! Jira can also be used to track the progress of a Tactic. To connect a Tactic to Jira, go to your Tactic, use the three-dot menu and hit "Connect to Integration".
Choose Jira and hit "Connect".
Next, fill out the information in the modal. First, select the Project in Jira that you want to track progress for.
Next, choose an Epic to filter by (if applicable).
Finally, choose how you want to track progress. You can choose to track by the percentage of completed issues, or the % of completed project points.
Hit Save!
Permissions with Integrations in Elate
In order for your teammates to connect and configure an outcome in Elate using a connected Integration, two things must be true.
They must have permission to edit the Outcome itself.
AND
They must have access to the Integration.
An Elate user has access to edit an Outcome if:
They are an Org Owner or
They are an Outcome Owner or
They are on the team responsible for the outcome.
An Elate user has access an Integration if:
They are assigned access to the Integration by the Integration Owner. See below for more on how to assign teammates to an Integration in Elate.
Commonly Asked Questions
Q: My date field is not being recognized even though it's on my ticket. What do I do?
A: If the date field is not being recognized, make sure it's on your tickets as a description field not a context field.
Q: I'm not sure I'm using the JQL function correctly. Do you know of any troubleshooting I can try or double check my function?
A: Yes! In Jira, navigate to a project board and select Issues on the left hand side. This is where you will be seeing all of the issues on that project. If it's on basic filter, you will not see the JQL function. In the top right, toggle from Basic to JQL. You will be able to test out your project and parent function here and are able to just copy and paste it from here.