GridPilot for Jira gives teams a spreadsheet-like way to query, organize, edit, save, share, export, and analyze Jira issue data without leaving Jira.
Open GridPilot for Jira from the Jira app navigation. The main screen contains the configuration controls, query results, saved view tools, collection tools, and pivot table options.
Use the Trust shield in the top toolbar to see a brief summary of how the app handles Jira data and saved configuration.
GridPilot displays the matching Jira issues in the results area.
The query results grid lets you:
Click a column header to sort results by that column. Click the same header again to switch between ascending and descending order.
If you manually move rows, GridPilot preserves your manual row order and pauses column sorting. To return to column sorting, either:
Editable fields can be updated directly from the results grid.
If you click away from a field without changing anything, the editor closes without saving.
Press Escape while editing to cancel the edit without saving. In fullscreen mode, the first Escape cancels the active field edit; when no field is being edited, Escape can exit fullscreen.
Some fields may not be editable because Jira does not allow editing that field for the issue, screen, project, or issue type. GridPilot follows Jira permissions and edit metadata.
Saved views let you reuse a GridPilot configuration.
A saved view can include:
To save a view:
New saved views start private. Existing views keep their current sharing settings when overwritten.
Use Manage Saved Views to:
Deleting a saved view removes only the saved GridPilot configuration. It does not delete or change Jira issues.
Saved views and collections can be shared with other users.
Sharing options include:
Permission levels:
Sharing a saved GridPilot item does not change Jira project permissions or issue permissions.
Collections help organize saved views and pivot tables into groups.
Use collections to:
Pivot tables summarize Jira issue data by rows, columns, values, and aggregations.
Use pivot tables to analyze work by:
The default aggregation is None, which keeps the initial pivot output close to the query results until you choose a summary option.
Pivot tables can be saved and added to collections.
Formatting rules help highlight important issues or fields.
Use formatting to visually flag items based on field values, such as:
Formatting can apply to rows or individual fields, depending on the rule.
Click Export CSV to download the currently visible results.
The export includes:
Exports use what is visible in the grid at the time of export.
Click Bulk edit to open Jira’s native bulk edit flow for the current result set.
Jira applies its normal project, issue, and field permissions before allowing changes.
Use fullscreen mode when you need more room for large result sets or wide tables.
While editing a field in fullscreen:
GridPilot runs on Atlassian Forge. Jira issue data is requested using the current user’s Jira permissions.
Saved GridPilot configuration is stored in Forge app storage. Some low-sensitivity UI state may be cached locally in the browser for resilience and convenience.
GridPilot does not replace Jira permissions. If a user cannot view or edit an issue in Jira, GridPilot should not grant access to that issue or edit.
The field may not be editable for that issue in Jira. Confirm the field is available on the issue’s Edit screen and that you have permission to edit the issue.
You may have manually moved rows. Manual row order pauses column sorting. Click a column header or click clear manual order to return to column sorting.
You may have view-only access to a shared view. Ask the owner to grant edit access if you need to change the saved configuration.
Check that the JQL is valid and that your Jira permissions allow you to view matching issues.
The CSV export uses the currently visible results. Refresh or rerun the query, adjust filters, and verify grouping or hidden done settings before exporting.