Manual ordering lets you set a fixed, custom order for a snapshot's level-1 rows by dragging them into place. Use it when the order you need can't be expressed by a JQL sort or by sorting on a field — for example, putting one key row at the top so it's the first thing a reviewer sees, or arranging rows by a priority that lives in someone's head rather than in a Jira field.
Unlike sorting on the page, a manual order is saved with the snapshot, shared with every page viewer, and kept when you take a new snapshot.
By the end of this page, you have a snapshot whose rows stay in the exact order you set, for everyone who opens the page.
Manual ordering is persistent and shared.
This is the opposite of sorting and filtering on the page, which is temporary and visible only to you. A manual order changes what every page viewer sees, and it survives page refreshes and new snapshots.
How it works
-
Turn on ordering mode
Above the first level of the snapshot, click the reorder arrows. A blue frame appears around the table to show you're in ordering mode.
-
Drag rows into the order you want
With ordering mode on, drag and drop rows to wherever you need them. You can move as many rows as you like in a single session — for example, drag IT sample 25 to the top, then arrange the rows beneath it.
-
Save the order
When you're happy with the arrangement, click Save. This step matters: if you don't save, the order is discarded and nothing changes for page viewers.
After saving, the order indicator changes from a white background to a grey background. The grey indicator is how you tell, at a glance, that manual ordering is active on this snapshot. From now on, everyone who opens the page sees the rows in the order you set.
Removing a manual order
To clear manual ordering and return the snapshot to its default order (the JQL or field sort), click the X on the order indicator. The grey indicator returns to white, and the rows fall back to their standard order.
What happens when you take a new snapshot
Taking a new snapshot keeps your manual order for every issue that was already present when you set it. Issues that existed before stay exactly where you put them.
Issues that are new in the snapshot (they didn't exist when you set the order) are added at the bottom of the table. To weave them into your order, initiate another manual reorder operation and save again.
Scope and limits
-
First level only. You can manually order the first level of a snapshot. In a multi-level snapshot you can still reorder, but only the level-1 items move; rows nested under them stay with their parent.
-
Up to 5,000 first-level rows. If a snapshot's first level has more rows than this limit, manual ordering is disabled for that snapshot. The limit is high enough that it doesn't affect the large majority of snapshots.
-
If the first level row is grouped , then the 5,000 limit applies on each of the groups (not on the overall number). So if you have to reorder a larder snapshot, consider grouping the first level.
-
What's next
-
Sorting, filtering, and grouping on the page — temporary, personal row manipulations that don't change the snapshot.
-
Field options: sort and don't-wrap — set a default sort when a field can express the order you need.
-
Grouping rows by a field — break level-1 rows into sections by a field's values.