Getting started with CrossView
CrossView is a cross-project request dashboard for Jira and Jira Service Management. It aggregates tickets from all your projects into a single view with filters, analytics, saved views, and export.
Getting Started
Installation
CrossView requires Jira Cloud (Standard, Premium, or Enterprise) and can be installed by a Jira site administrator.
First Use
On first load, CrossView shows all non-done tickets sorted by most recently updated, with 8 default columns: Key, Summary, Project, Status, Priority, Assignee, Created, and Updated. The default analytics charts (KPI tiles, status breakdown, and project volume) appear above the grid.
Everything you see is customizable — columns, filters, charts, and the JQL query itself. Your preferences persist automatically across sessions.
Features
Cross-Project Grid
One table showing issues from all your Jira and JSM projects. Sort by any column, paginate through results.
Filter Chips
Layer filters on top of JQL — Status, Priority, Project, Assignee, Reporter. No syntax editing required.
Analytics Dashboard
Six chart types computed from your current tickets. Toggle and collapse as needed.
Saved Views
Save any dashboard configuration. Private or public. Load, modify, and share with your team.
WYSIWYG Export
Export exactly what you see to CSV or XLSX. Visible columns, current sort, applied filters.
Column Preferences
Choose which columns to show, including custom fields. Per-user persistence across sessions.
Ticket Grid
The grid is the core of CrossView. It displays tickets from all projects you have access to in a single sortable table.
Sorting: Click any column header to sort. Click again to reverse direction. The current sort column shows an arrow indicator (↑ or ↓).
Pagination: CrossView loads 100 tickets per page. If more tickets match your query, a "Load more" button appears at the bottom. The ticket count shows how many are loaded and whether more are available.
Issue links: Click any issue key (e.g., IH-2) to open it in Jira's native issue view. Hold Ctrl (or Cmd on Mac) to open in a new tab.
Filters
Filter chips let you narrow results without editing JQL syntax. Filters are combined with your JQL using AND logic.
Adding a filter: Click + Add filter in the filter bar. Choose a field (Status, Priority, Project) and select one or more values, or choose "Assigned to me" / "Reported by me" for quick personal filters.
Removing a filter: Click the × on any chip, or click Clear all to remove all filters at once.
How filters combine with JQL: If your JQL bar contains project = IH and you add a Status filter for "Open", the effective query becomes (project = IH) AND status in ("Open"). ORDER BY clauses are preserved.
Columns
Click Columns (N) in the header to open the column picker. Toggle visibility of standard columns and your tenant's custom fields.
Standard columns: Key, Summary, Project, Status, Priority, Assignee, Reporter, Request type, Created, Updated.
Custom fields: Any custom fields in your Jira instance with supported schema types (text, number, date, user, option, array) appear in the "Custom fields" section of the picker.
Persistence: When no saved view is loaded, your column choices save to your personal preferences and persist across sessions. When a saved view is loaded, column changes are part of the view's state — use "Save changes" to update the view.
Analytics Dashboard
The analytics band sits between the filter bar and the grid. It computes charts from the currently-loaded tickets — the same data the grid shows, with the same filters and JQL applied.
| Chart | What it shows |
|---|---|
| KPI Tiles | Total tickets, unassigned count, average age in days, oldest ticket age. Unassigned and oldest-ticket tiles highlight in amber when values warrant attention. |
| By Status | Donut chart showing ticket distribution across statuses with a legend. |
| By Project | Horizontal bar chart comparing ticket volume per project. |
| By Priority | Bar chart showing ticket count per priority level. |
| By Assignee | Horizontal bar chart showing tickets per person (top 15, with "Others" grouping). |
| Aging | Histogram with age buckets: <1 day, 1–3 days, 3–7 days, 7–14 days, 14–30 days, 30+ days. |
Toggling charts: Click Charts (N) in the header to choose which charts are visible. Your chart selection is saved as part of saved views.
Collapsing: Click the ▾ Analytics bar to collapse the entire analytics section and give the grid full screen height. Click ▸ Analytics to expand again.
Saved Views
A saved view captures your entire dashboard state — JQL, filters, columns, sort order, and chart selection — so you can return to it later or share it with colleagues.
Creating a view: Configure your dashboard the way you want it, then click the view selector in the header → + New view from current state. Give it a name and choose Private (only you) or Public (anyone on your Jira site).
Loading a view: Click the view selector dropdown and click any view. The dashboard replaces its current state with the view's saved state.
Modification tracking: When you change anything after loading a view, a red dot (●) appears next to the view name. If you own the view, a Save changes button appears. If it's someone else's public view, you get Save as new instead.
Editing metadata: Click the pencil icon (✎) next to an owned view to change its name, description, or visibility.
Deleting a view: Click the × icon next to an owned view. A confirmation prompt appears. Deleted views cannot be recovered.
Export
Click the ⋯ menu in the header and choose Export as CSV or Export as XLSX.
Exports are strict WYSIWYG — only the visible columns, in their current order, with the current sort and filters applied. The exported file contains exactly the rows and columns you see on screen.
File naming: Files are named crossview-{view-name}-{date}.csv (or .xlsx). If no view is loaded, the name is crossview-export-{date}.
Excel compatibility: CSV files include a UTF-8 BOM for correct encoding in Excel. XLSX files have auto-sized column widths.
JQL Reference
The JQL bar accepts any valid Jira Query Language query. CrossView's default query is:
statusCategory != Done ORDER BY updated DESC
This shows all non-resolved tickets across all projects, most recently updated first. You can change this to any valid JQL — project-specific, assignee-specific, date-filtered, or complex boolean expressions.
Running a query: Edit the JQL bar and press Enter or click Run.
Combining with filters: Filter chips add AND clauses to your JQL automatically. The ORDER BY clause is preserved.
Example queries
| Use case | JQL |
|---|---|
| All open tickets | statusCategory != Done ORDER BY updated DESC |
| Single project | project = IH ORDER BY priority ASC |
| My tickets | assignee = currentUser() ORDER BY updated DESC |
| High priority unassigned | priority = High AND assignee is EMPTY ORDER BY created DESC |
| Created this week | created >= startOfWeek() ORDER BY created DESC |
| Multiple projects | project in (IH, THAR, CUL) ORDER BY updated DESC |
Data & Privacy
CrossView is built on Atlassian Forge and runs entirely within Atlassian's infrastructure. No data is sent to NeuralWeaves or any third party.
What CrossView stores
| Data | Purpose | Retention |
|---|---|---|
| User preferences | Column visibility per user | Until app uninstall |
| Saved views | Dashboard configurations | Until deleted or app uninstall |
| Ticket cache | Performance optimization | 5 minutes (auto-expires) |
| Field metadata | Column picker and filters | 30 minutes (auto-expires) |
CrossView uses read-only API scopes. It never creates, modifies, or deletes any Jira data.
Full details: Privacy Policy · Terms of Service
Frequently Asked Questions
Support
For questions, bug reports, or feature requests, contact us at:
Email: support.marketplace@neuralweaves.com
When reporting an issue, please include your Atlassian site URL, the steps to reproduce, and any relevant screenshots or error messages.
Service Level Agreement: neuralweaves.com/marketplace/sla