Release notes v2.1.0

New

Two ways in

• Reorder child issues — in any issue’s ••• menu, opening in a pop-up on that issue: an epic’s child issues, or a story’s sub-tasks. The breadcrumb zooms out to the whole space.
• Issue Order for Jira — under Apps: choose a space and work on all of it. It reopens on the space you used last.
• Jira spaces — software and business spaces, company-managed and team-managed.

The outline

• One numbered outline in Rank order — epics 1, 2, 3, child issues 1.1, sub-tasks 1.1.1, the same order as the epic’s child list, boards and backlogs. Numbers count done issues too, so hiding them never renumbers anything.
• Show — epics only, down to child issues, or down to sub-tasks, with each level named after the space’s own work types.
• Without an epic and Under epics in other spaces — sections at the bottom, so every issue in the space has a place.
• Find, Hide done and Numbers — find an issue by key or summary; hide done issues (on by default); show or hide the numbers.
• Up to 1,000 issues per list, with the list saying so when there are more. With Hide done on, a longer list shows its first 1,000 open issues.
• Light and dark, matching your Jira theme, with icons drawn to match Jira’s standard work types (epic, story, task, bug, feature, sub-task); other types get a neutral grey icon.

Dragging and ticking

• Tick by clicking, or press and sweep down to tick a run of issues; Shift-click ticks a range. Ticks hold one level at a time.
• Drag a ticked row to move every ticked issue, gathered together; an unticked row’s grip drags just that row. A line shows where they’ll land.
• Drop onto an epic to move issues into it, or onto a story to move sub-tasks under it. Hovering a folded epic while dragging opens it.
• Each row’s ••• menu — Move up, Move down, Move to top, Move to bottom, Move to… and Open in a new tab.
• Keyboard support — arrow keys move through the outline, Space ticks, Enter opens and closes, and Shift+F10 opens a row’s actions.

Move to…

• Child issues to another epic, in this space or, with Other spaces, in another company-managed space; or out of their epic, to Without an epic.
• Sub-tasks to another issue in the same space. On sites with a level above epics, epics to another initiative, from their current initiative’s Reorder child issues.
• At the top or At the end of the new parent.
• Refusals shown before you choose — a parent the issues can’t go to is greyed out with the reason, such as Already here. or Team-managed spaces keep parents and children in the same space. With Hide done on, done epics aren’t offered.

Sort

• Up to three levels — for example Priority, highest first, then Due date, soonest first. Each level picks its direction in its own words.
• Fields every space has — Rank (Jira’s default order), Priority, Due date, Overdue, Status, Created, Updated, Resolved, Summary (Step 2 before Step 10) and Key.
• The space’s own fields — number, date, choice, version, component and label fields from its edit screens, such as Story Points and Start date. Fields holding people are never read.
• Sorts what you tick — a ticked epic’s child issues, a ticked story’s sub-tasks, or just the ticked issues within the places they hold. With nothing ticked, the child issues in each epic on the Apps page (or the epics themselves), and an epic’s child issues in its pop-up.
• A live preview in the outline, with how many issues change place, before the sort goes into your draft. Hidden done issues keep their places.

Priority lanes

• One switch — tick Priority lanes in the toolbar and each epic’s child issues, and their sub-tasks, are put in priority order, grouped into lanes (or the epics too, with Child issues and epics), as part of your draft. Untick it to take that back.
• Drag into another lane to change an issue’s priority as well as its place; the new priority is saved with the order.
• Lists left out of order say how many — n of m out of priority order — and Put in lanes sorts them into lanes, keeping your order within each lane.
• Not placed yet — issues new since you last ordered a list wait at its top: Place by priority or Keep where they are.

Draft, Review and save

• Nothing changes in Jira until you save — every change is a draft, marked in place: the new number in blue, the old one struck through, a note with × to undo it, and a faint line where an issue left.
• Review shows only your changes. Undo and redo work with ⌘Z and ⇧⌘Z (Ctrl+Z and Ctrl+Y on Windows), and Discard clears the lot, with Restore changes straight after.
• One save writes everything — new parents, new priorities and the new order, as Jira’s own Rank. Only the issues that must move get a new Rank, so the rest of your boards and backlogs stay as they were.
• A teammate’s new order isn’t undone — the save first checks every list it touches. If the order changed in Jira meanwhile, nothing is saved, and Refresh puts your changes back where they still fit. Each list is checked again just before it’s ranked, and left as it is if it changed during the save.
• Every new order is read back from Jira after the save. Anything Jira refused stays in your draft, with the reason.

Safety net

• Unsaved changes survive a closed tab — they’re kept in your browser (issue keys, priority names and sort names, never summaries) while you edit, and coming back offers Restore unsaved changes or Discard them.
• Lists that changed in Jira since get back only your own moves, so a teammate’s work stays.
• Kept for 14 days, and cleared when you save, discard or leave without saving.
• Leaving asks first — Close in the pop-up and switching space on the Apps page both ask before unsaved changes are lost.

Speed

• Big spaces load fast — the app finds a list’s issues in one quick search, then reads them several at a time.
• Your last space opens straight away, while the full list of spaces loads behind it.
• A fresh view when you come back — returning to the tab quietly reloads the outline from Jira if it last read a minute or more ago, but only with nothing unsaved and nothing to undo, and not while a pop-up or the Sort bar is open.

Permissions and data

• Acts only as you — Jira’s own permissions apply, so people reorder only the issues they could already rank. Reordering needs Schedule issues and Edit issues.
• Stores nothing outside your browser — no database and no server of its own. It runs on Atlassian, with nothing sent outside it.