- Manually Adding Projects
- Linking Issues Using JQL
- Adding Items Using Basic Search
- Use Case Example
Manually Adding Projects
If you know what issues you want to link to the key result, you can manually add these via a basic search. Start by naming your key result, then click "+ Add an integration". This will bring up a search bar where you can perform a basic search that will search your JIRA instance. We will provide issues that match the search, which you can then click to add to your key result.
In this example, four issues were chosen. After clicking “Save” the completion of these issues will automatically be tracked in Betterworks. I can add comments on my progress if I want provide any status updates, but the completed work will automatically be captured. As I complete these issues in JIRA, they will automatically be updated in Betterworks.
Linking Issues Using JQL
Often when you setup your objectives, not all of the issues in JIRA have been established. Examples include fixing bugs over the course of the quarter or all of the issues linked to an Epic. You can use our “Continuously populate key result with query results” in these instances.
Switch from a basic search to a JQL query and utilize JQL to match any issue that would be pertinent to the key result you are linking to. After inputting the JQL query be sure to check "Continuously populate key result with query results". When this box is checked, Betterworks will automatically add any new JIRA issues that match the criteria of your JIRA query. For example, if I get assigned a new bug to fix, that issue will automatically be added to my key result for tracking.
If you are well versed in JQL, that is great! Feel free to search directly in Betterworks like you would in JIRA using JQL. If you could use a bit more practice on JQL, no problem! Any basic search in JIRA can be converted to a JQL by clicking "Advanced" within JIRA. You can then copy this string and paste it into our search bar as a JQL query.
The Betterworks JIRA integration allows you to search for and pull data in from JIRA by writing a basic search or creating a JQL query.
Below are a few samples of JQL queries that you can leverage when creating your OKRs.
- Sample JQL for "Work assigned to me"
assignee=”[name]" AND updated>[quarter_beg] AND labels=OKR
- Sample JQL for "Epics for my team"
issuetype=Epic and project in ([project_team_name]) AND "Planned \"Done\" Date”>[quarter_beg] AND "Planned \"Done\" Date”<[quarter_end]
- Sample JQL for "Epics for my initiatives"
issuetype=Epic AND Initiative in ([initiative_name]) AND "Planned \"Done\" Date”>[quarter_beg] AND "Planned \"Done\" Date”<[quarter_end]
- Sample JQL for "Epics I have written"
issuetype=Epic AND reporter=”[name]" AND "Planned \"Done\" Date”>[quarter_beg] AND "Planned \"Done\" Date”<[quarter_end]
For a more in depth review of JQL, see JIRA's website.
Adding Items Using Basic Search
If you know what issues you want to link to the objective, you can manually add these via a basic search. Start by naming your key result in the creation stage, then click the JIRA icon in the integration option panel. This will bring up a search bar where you can perform a basic search of your JIRA instance. Betterworks provides issues that match the search, which you can then click to add to your key result.
Use Case Example
One great use case for this is for an engineer to track bugs that they have to squash. In the following example, Damon is tasked with fixing 25 bugs over the course of the quarter. The JQL query in this case will have the assignee set to Damon, a label string that captures the issue as a bug and the resolution as unresolved. Combining these elements in a JQL string will automatically keep track of this objective without needing to manually update the Betterworks system.
Product managers can also get a lot of value out of using JQL to track the work being done to deliver a new feature. By setting up a JQL to track a specific Epic in JIRA, all tickets matching the query are automatically linked to the key result in Betterworks. As issues are created that match the query, they are linked to key result to be tracked for progress. Using this integration gives you and others in the organization a way to track how development is going on the features you’re looking to ship - simply have each contributor use a JQL string to identify issues in the epic which are assigned to them to get visibility into overall progress.
Can I update a JIRA ticket from Betterworks?
Not at this time. The JIRA integration can only pull information from JIRA. Users are not able to push data back to JIRA.
My JIRA integrated item isn't updating; how do I get it to work?
There are few items to immediately check:
- Has the associated key result's due date already passed. JIRA-integrated key results don't update after the due date. You will need to manually sync the key result by clicking additional actions and then sync.
- Loop in a member of your team who has access to the JIRA user account so they can see if the credentials are up-to-date.
- Does your JIRA issue still exist?
- Is your JQL string is complete and correct?
Can I use the JIRA integration for a select group of users?
No. When the JIRA integration is activated, all users will have the opportunity to link JIRA issues in Betterworks.
Can I see the full details of a JIRA ticket through Betterworks?
No. We only access three standard items via the JIRA integration: Issue ID, Issue Title, Issue Resolution (issue open/closed). Additionally, our integration is able to pull data from any custom fields you've set up in order to more accurately inform progress on the integrated key results.
Note: Users can not see any other ticket data (such as description) from within Betterworks.
Can SSO be used to enable the Jira Integration?
Not at this time. It's not possible to use SSO to enable the Jira integration. We recommend either using a non-SSO account or looking into an official JIRA sanctioned way of managing this.