Child Issue Order: Reorder Epic Children by Drag & Drop in Jira

Drag an epic's child issues into order right on the epic. Each move is saved as Jira's own Rank, so the child list, sub-tasks, boards and the backlog show the same order.

  • For Jira Cloud
  • Free up to 10 users
  • Built on Atlassian Forge
  • Saved as Jira’s own Rank
On this page
  1. Drag and drop on the epic itself
  2. Jira’s own Rank, not a private list
  3. Boards and the backlog follow
  4. A button for every move
  5. No permission? The order stays put
  6. Also included
  7. Runs on Atlassian
  8. Related apps
  9. FAQ

Child Issue Order puts the child issues of an epic — or the sub-tasks of a story — in the order you want, right on the issue. Drag a row or press its buttons: each move is saved at once as Jira’s own Rank, so Jira’s child list, boards and the backlog follow.

Drag and drop on the epic itself

A panel on the epic lists its child work items in Rank order, with status and assignee. Drag a row where it belongs: each move is saved at once, with your own Jira permissions. There is no separate page to open and no Save button to forget.

Jira’s own Rank, not a private list

The order is saved as Jira’s Rank, so Jira’s Child work items and Subtasks lists and any filter sorted by Rank show it too. It works for sub-tasks and in Jira Service Management.

Boards and the backlog follow

Plan the epic once. The sprint backlog, boards and filters sorted by Rank list its work in the same order, so the team picks up the next item with no second list to keep in sync.

A button for every move

Every row has Move up and Move down buttons and a menu with Move to top, Move to bottom and Open, so no drag is needed and the keyboard works too.

No permission? The order stays put

Moves are made as you, never as the app. Without Jira’s Schedule issues permission the panel shows the order read-only and says who can grant it.

Also included

  • Epics and any parent: stories, tasks, bugs and sub-tasks.
  • Company-managed and team-managed projects, and sub-tasks of Jira Service Management requests.
  • Large epics: 50 children at a time with Show more, plus the total count.
  • Safe when others edit: if someone else changes the order meanwhile, the panel says so and shows Jira’s order.
  • Light and dark themes, narrow and wide issue views.

Runs on Atlassian

Child Issue Order is built on Atlassian Forge and makes no calls outside Atlassian. The child issues are read as you and not stored; each move is one rank change made as you, with your Jira permissions. See the privacy policy.

  • Priority Board — prioritize the backlog by dragging issues between priority columns and ranking them.
  • JQL Blocks — build searches like parent = CIO-1 ORDER BY Rank from blocks.
  • Deadline Tracker — overdue and upcoming work across projects on one board.

Searching for an epic’s children in JQL: JQL for parents, epics and linked issues.

Frequently asked questions

Which Jira permissions does the app ask for, and why?

Read Jira work, to list the child issues of the issue you open and to check your permissions; Jira Software issue write, only to change an issue's Rank when you move a row; and app storage, for two small marks per person (the first tip was shown, when to ask for a review). Every read and move is made as you, so you never see or change more than in Jira.

Where is my data stored?

Issues stay in Jira and are read as you each time the panel opens; the app keeps no copy of them. It stores only the two marks per person above, inside your Atlassian site. Nothing leaves Atlassian and Simplify has no server.

How much does it cost?

It is free for sites with up to 10 users. Larger sites pay per user through the Atlassian Marketplace, after a free 30-day trial.

Does the order show anywhere else in Jira?

Yes. The order is Jira's Rank, so Jira's Child work items and Subtasks lists, boards, the backlog and any filter sorted by Rank show it too. The app keeps no list of its own.

Who can change the order?

People with Jira's Schedule issues permission in the project, the same permission that ranks issues on a board. Others see the order read-only, with a message that says who can give them the permission.

Does it work for sub-tasks and Jira Service Management?

Yes. On a story or task the panel lists its sub-tasks, and on a Jira Service Management request the sub-tasks of the request. It works in company-managed and team-managed projects. Ordering needs Jira's Rank field, which comes with Jira Software.

Get Child Issue Order

Free up to 10 users. Install it from the Atlassian Marketplace.