A very useful tool used to search for Jira Software issues is JQL, which stands for Jira Query Language. Jira Software users can use JQL to create database queries to provide faster access to information in Jira. If you have a technical background and are familiar with SQL, then you have a head start because Atlassian's implementation of JQL is similar. To learn more about JQL and how to use it with Jira Software, please consult our Jira documentation:
JQL functions the same way in Jira Align as it does with a Jira Software Advanced Search--it allows you to create custom queries that search for data in Jira Software. When a JQL query is used in Jira Align, it returns data directly from Jira Software and performs a one-way sync to Jira Align (i.e., data is pulled from Jira into Jira Align, but not pushed from Jira Align into Jira). For example, you can use a JQL query to search for a specific sprint in Jira Software, and have the found sprint added to Jira Align's backlog and/or Sprint grid.
The primary use case for JQL queries is to search for legacy data in Jira Software and have it pulled into Jira Align. For example, let's suppose Jira Software was integrated with Jira Align via the connector on a specific date, such as 01/01/18. In this case, Jira Software and Jira Align data has been syncing since the integration date, but what if you wanted to sync data that was created before the integration date, for example from the year 2017? You would need to create a JQL query that searches for your target data in Jira Software and syncs it with Jira Align.
Best Practice: We recommend that you build the query statement first in Jira using a Jira Advanced Search, and test it to make sure it returns the target data. Query strings are easier to build directly in Jira, as Jira will suggest operators and spaces to use in the string. Once tested, the string can be cut and pasted into the Jira Integration page of Jira Align to conduct a search.
Follow these steps to search for and sync legacy Jira Software data with Jira Align:
*An Alternative to the custom JQL inside of Jira Align is utilizing a Bulk Edit in Jira. The Jira bulk update is described here:
The main reason to utilize a Bulk Edit in Jira instead of a custom JQL in Jira Align is that the custom JQL in Jira Align will lead to additional API load on the integration while the Bulk Edit in Jira will send updates to Jira Align during Jira Align's routine queries for issues. The Jira Align custom JQL functionality also does not allow multiple custom JQLs to be queued in a row, while you can make multiple Bulk Edits in Jira. It is recommended to Bulk Edit the issues in Jira with a Comment such as "Force Sync to Jira Align: Please Ignore" in order to flag Jira issues as updated for the integration to pick them up and send the updates to Jira Align.
It is highly recommended to disable email notifications for the update to avoid any necessary spam to users:
Disable notifications for bulk operations - You can disable mail notifications for a particular bulk operation by deselecting the Send Notification checkbox in the bulk operation wizard. For this option to be available, you must be an administrator or project administrator of all the projects associated with your selected issues.
If your organization has a workflow enabled to watch issues after a bulk update you can utilize the following steps to stop watching any bulk updated issues:
To stop watching multiple issues:
Tim KeyesAtlassian Team
(Or, What to expect when you’re expanding.) Once you've completed your Jumpstart, or your initial assessment of Jira Align, you'll start to think about how you can roll it out to the rest of your e...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events