Columns
A view can show up to 40 columns next to the tree. Select + Column at the end of the grid's header to open Add a column, then search for a field or a column type by name.
On this page
Field columns
Any Jira field, system or custom, can be a column. That includes fields from Jira Software, Jira Service Management, Assets and other apps. Values show as Jira shows them to you: people by name, Assets objects by name, and other apps' values by their name, key or label.
You can edit a field in place when Jira lets you edit the issue. See Editing cells. You can also edit simple text or number fields from other apps.
Type, status, assignee and priority columns can show icons instead of text: use Show as icons in the column's header menu.
Totals
A column named Σ followed by a field's name, such as Σ Story Points, adds up a number or time field over each branch. A row's total is its own value plus the values of every row below it. An issue that appears twice under one row is counted twice. To count each issue once, or to count only the leaves or the children, write a formula instead.
By default, a total counts only the issues the person viewing it can see. A Jira admin can let chosen number fields count the hidden issues too. See Hidden issues in totals.
Progress
A progress column shows how much of what sits below a row is done, as a bar and a percentage. The picker offers these ready-made kinds:
| Column | How it counts |
|---|---|
| Progress | The share of issues at the bottom of the sub-tree whose status is in the Done category. |
| Progress (status category) | As above, and an issue in progress counts as half done. |
| Progress (time) | Time spent over time spent plus time left, for the row's issue and everything below it. |
| Progress (time, else status) | Time where it is tracked, otherwise done or not. |
| Progress (by Story Points) | The done share of the story points below, when your site has a story points field. |
Progress options… in the header menu changes how a column counts. Unless the column counts time, you can weight each issue by a number field, and an issue without a value then counts for nothing. Statuses with a share of their own lets you give chosen statuses a fixed done share, for example 80% for In Review. Other statuses count according to their category.
Time and history
These columns read each issue's history using your access:
| Column | What it shows |
|---|---|
| Time in status… | The time spent in the statuses you pick, added up, or the cycle time from the first In Progress status to Done (up to now if the issue isn't done). Counts calendar time and can total over the sub-tree. |
| Date entered a status… | When the issue first or last entered a status. An issue created in that status entered it when it was created. |
| Logged work… | Time logged at any time, in the last days or between two days, by everyone or by the people you pick, with an optional total over the sub-tree. Only work logs you can see are counted. |
A view can have up to 3 columns that read each issue's history, comments or logged work, and they work on hierarchies of up to 5,000 issues.
Queries
Matches a query… shows Yes or No on each row, for a JQL query (which issues match) or a tree query (which rows match). Jira runs the query as you, so rows match only what you can see. A view runs at most 5 JQL or tree queries in its columns.
Values you keep in the hierarchy
| Column | What it holds |
|---|---|
| Notes | Your own text per issue or folder, up to 2,000 characters, kept with this hierarchy. Everyone who can view the hierarchy sees the notes. |
| App field… | A typed value per issue or folder: text, number, date, person, or a choice from a list of up to 30 options. App fields sort, filter, export and work in formulas, rules and grouping. People with Edit access can change the values. |
Notes and app field values belong to the hierarchy and don't change anything in Jira.
If you later change an app field's kind, existing values stay as they are, and a value that no longer fits stays marked until someone changes it.
Information about the row
| Column | What it shows |
|---|---|
| Outline number | 1, 1.1, 1.2 and so on. |
| Children | The number of issue rows directly below. |
| Leaves | The number of issue rows at the bottom of the sub-tree. |
| Row ID | The row's number in this hierarchy. |
| Item ID | What the row shows, as kind/id, such as issue/10001. |
These come from the tree as you see it and read nothing from Jira.
More issue information
| Column | What it shows |
|---|---|
| Last comment | Who wrote the latest comment, when, and the start of what they wrote. |
| Images | Thumbnails of the images attached to the issue. Click one to see it larger, and use the arrows to go through the others. |
| Linked issues | The issues linked to it, by kind of link. |
| Sub-tasks | The keys of its sub-tasks. |
| Project category | The issue's project category. |
| Raw value… | A field's value as Jira stores it, with ids, keys and every part. |
| SLA columns | For Jira Service Management, each SLA field offers its time remaining, whether it breached, its goal and the time elapsed, as of when the grid loaded the issue. |
Test run
Test run of a write-back… shows, on each row, the value a write-back would set, written as old value → new value. Nothing is written to Jira. A test run covers the first 5,000 rows.
The column header menu
Each column has a menu on its header. What it offers depends on the column:
- Sort ascending, Sort descending and Clear sort. Sorting by a column is a transform, so it changes only your view. Formulas, totals, progress and notes sort by the value they show.
- Group by this column and Stop grouping.
- Filter by value… lists the values among the rows shown, most common first, with their counts. Pick the ones you want and select Apply. The column's title then says "(filtered)".
- Rename… gives the column a name of its own, and Use its own name goes back to the field's name.
- An entry to change the column's settings, such as Edit formula…, Progress options…, Edit query… or Change field….
- Save to library… keeps the column under a name to reuse in any hierarchy.
- Show as icons or Show as text, for type, status, assignee and priority.
- Move left, Move right, Duplicate, Fit width and Remove.
To resize a column, drag the handle on the right of its header, or focus it and use the arrow keys. A double-click or Enter on the handle fits the column to its content. Widths are kept with the view.
The saved-column library
Save to library… keeps a column, often a formula, under a name and an optional description. Tick Share with everyone who can use the app to share it. Jira admins can limit who may share saved columns in Automation permissions. The library keeps the column's definition, not its values, so each person who adds it sees what Jira shows them.
Saved columns appear in the Add a column list as Library · yours, Library · yours, shared or Library · shared. The app also includes a starter set, marked Library · starter:
| Starter column | What it shows |
|---|---|
| Age in days | Days since the issue was created. |
| Days since last update | Days since the issue last changed. |
| Overdue | Not done and past its due date. |
| Remaining estimate total | Time left over the issue and everything below it. |
| Time spent total | Time spent over the issue and everything below it. |
| Progress by story points | The done share of the story points below. |
| Cycle time | From the first In Progress status to Done. |
| Logged in the last 7 days | Work logged by anyone in the last week, with its total. |
| Assigned to me | Yes for issues assigned to the person viewing. |
Questions about the app? Write to info@plugincraft.ca.