General - Import
Import Jira issues using favorite Jira filters or build JQL expressions.
You can even save your JQL expression as a new filter.
When issues are imported you can edit available fields.
With Refresh button you can check Jira for any updates in imported issues.
Import is the first section of General view of Excel 365 Connector.
It’s marked green color on the below screen.
Import modes:
Standard mode
You can import issues:
From Jira filters
By building personalized JQL
Importing issues using Jira filters:
In active “Filter” tab view. (1)
Select filter from dropdown. (2)
Displayed filters are your favorite filters in Jira. To make a filter a favorite, click the star icon next to its name in Jira.
To refresh the list of favorite filters, click the refresh icon at the bottom of the filters list. (3)
Use the “Import” button to fetch issues
Use saved column order
A Jira filter can remember the order of its columns. Turn on Use saved column order to import issues with the columns arranged exactly as saved on the selected filter — without changing which fields are shown.
There are two scenarios when importing issues while trying to preserve the selected filter column order:
If the
use filter column ordercheckbox is enabled (2) and the selected filter (1) has a saved column order, the issues are imported (3) into the sheet using the column order defined in that filter configuration.If the filter does not have a saved column order (or it is a system/default Jira filter) (4), the checkbox is disabled (5). In this case, issues are imported (6) using the column order from the currently selected schema, and it is not possible to save a custom column order for default Jira filters.
Import issues using JQL:
Select JQL tab. (1)
Input JQL language expression. (2)
Please note that when switching from the Filter tab to JQL, the selected filter will be automatically translated to JQL, allowing you to make changes smoothly.
Optionally: you can save your JQL expression as new Jira filter. (3) General - Import | Saving JQL expression as filter from Excel 365 Connector
Use the “Import” button to fetch issues (4)
In both methods - importing issues using a filter or a JQL query - the final step is to click “Import” (1) button to fetch issues. All issues matching criteria will appear on the sheet, with default set of columns.
If you find the need to update the current view, the "Refresh" (2) option can be a valuable tool. Additionally, it proves useful in the event of an error during data editing in the spreadsheet, allowing you to reset or reload the information for accurate and up-to-date records.
To check for updates in issues shown on the sheet, use the Refresh (2) button. It checks only the issues currently visible in the sheet.
To check for new issues, use the Import (1) feature. It retrieves all issues from the selected filter or JQL query, including newly created ones.
Tip 1: It is a good idea to check for updates, before making your own changes. Especially, if you didn’t make any changes for a while, because your data might be outdated.
Tip 2: Consider adding ‘fetch fresh issues’ to your routine, when you open the spreadsheet.
Tip 3: You can always open a new worksheet and check for the filter/jql results.
More info : Refreshing sheet
After importing data to Excel, connection icon will change:
From Not Managed (1) into Managed (2).
Connection icon indicates that there is a metadata available for currently active worksheet
Another thing that appears after importing issues is the Last used filter (1). If the data was imported by using JQL tab view, the Filter from JQL label will be displayed (2)
After Excel will restart, if the issues were fetching through the Filter, the Last used filter it will be displayed as the active filter(1), if by the JQL - will be open with label name: Filter from jql (2). After clicking on the name it will open the JQL</> tab with a last used query.
When app is open for the first time on worksheet, then first “Reported by me” filter will be open with no Last used filter label.
If new sheet or app is open for the first time on, then first “Reported by me” filter will be open with no Last used filter label.
The Last used filter will be kept until the data is re-imported.
Saving JQL expression as filter from Excel 365 Connector
When you build your own JQL to find related issues, you can use an option “Save as filter”, to use it in future. In the pop up window you need to add a name for your new filter (1), then set the checkbox responsible for Favorites (2) and click Save (4). Additionally, you can enable “Save column order for that filter” (3) to store the column order from the current schema.
This way you created a new filter in your Jira instance.
The Time tracking field cannot be saved in a column order: “Time tracking field is not supported for saving column order. Hide this field to save column order for this filter.” (5)
Read-only mode
If you choose read only mode, you won’t be able to edit imported issue.
Use this option to analyze large sets of data, limit is 100 000 issues.
Before clicking Import you can enable “Read only” (1) toggle.
When you import issues to sheet without “Read only” checkbox, this checkbox will disappear - to avoid data mismatch.
Fetching issues in read-only mode allows you to pull raw issue data from Jira. Be aware using this mode, that worksheet will not be managed by Excel 365 Connector and changes will not be tracked. Therefore you won't be able to send any changes to Jira.
Refresh (2) button is disabled in this mode, you are only able to view your issues (4) after clicking Import (3).
With Update 2.4.0 EC365 has received Excel dropdown list support .Dropdown list support
Unbound JQL in Jira Cloud
In Jira Cloud, a Jira Query Language (JQL) query is considered unbound when it is not constrained by required search boundaries. This usually happens when a query is too general (e.g., missing filters, project scope, or other constraints), which can lead to lower performance or the query failing to execute.
If a user has a saved filter containing a JQL query such as ORDER BY key (1), it is treated as unbound when used in the application. This means the query does not include sufficient search constraints and therefore cannot be used outside Jira until it is updated to include proper limits.
When navigating to the filter selection dropdown, unbound filters appear in the list but are disabled and cannot be selected (2). They remain blocked until the JQL is updated in Jira.
Hovering over a disabled filter shows a tooltip explaining the restriction (3)
In the JQL tab, a warning icon (4), indicates that unbound queries are no longer usable in their current form and require updates in Jira.
If a user tries to import an unbound JQL manually via the input field (5) and the Import button (6), the operation is blocked and a validation error popup is shown (7).
Clicking the warning icon opens an informational modal (8) provides additional details and a Learn more button (9), which redirects to Improve Jira issue export experience due to JQL search API.
What next? After you import issues you can edit them or create new issues. To send those changes to Jira you need to export changes: General - Export