FAQ

Setting it up

Is there anything to configure after installing?

No. The app has no settings screen and adds no admin page to Jira. What each person can do with it is decided by the Jira permissions they already have. See the Admin guide.

Who can use it?

Everyone who uses Jira on the site, once a site admin has installed it; there is nothing to set up. It acts as each person, so Jira’s own permissions decide what they can do. Reordering needs Schedule issues and Edit issues in the space, and so does moving an issue to another parent, because the app ranks it where you put it. A new priority needs Edit issues. Without them, the order shows but can’t be changed. See the Admin guide.

Can I restrict it to certain spaces?

Not from inside the app, because there is nothing to configure, and a Forge app is installed for the whole site, not per space. Jira’s own permissions are the control: someone without Schedule issues and Edit issues in a space can see the order there but can’t change it with the app either.

Will it slow my Jira site down?

It runs on Atlassian’s own infrastructure and does something only while someone has it open, from that person’s browser. It adds no backend, no background jobs and no triggers, just two entries: Reorder child issues in an issue’s ••• menu, and Issue Order for Jira under Apps.

Does it work on Jira Server or Data Center?

No. It’s built on Atlassian Forge, which is Cloud only.

Where do I open it from?

Two places: Reorder child issues in an issue’s ••• menu, which opens a pop-up on that issue, or Issue Order for Jira under Apps in Jira’s sidebar, a full page where you choose a space. See Where to open it.

The order in Jira

Does the new order show on boards and backlogs?

Yes. A save writes Jira’s own Rank, the one order that the epic’s child list (“Child work items” in Jira’s newer screens), boards and backlogs all sort by. Only the issues that must move get a new Rank, each placed next to its neighbour in the list, so issues you didn’t touch keep their places on your boards. A board whose filter is ordered by a field other than Rank shows that field’s order instead.

Can my teammates see the new order?

Yes, once you save. It’s Jira’s own order, so everyone who can see those issues sees it, in Jira and in Issue Order for Jira. Until then your changes are a draft in your browser, and nobody else sees them.

Does anything change in Jira before I press Save?

No. Drags, Move to…, Sort… and priority-lane changes all wait in your draft, and Discard drops them. Save changes writes them: new parents, new priorities, then Rank. A save can’t be undone, so Review shows exactly what it will change first. See Review and save.

What if a teammate changes the order while I’m working?

Before writing anything, a save reads again every list your changes touch. If one has changed, nothing is saved, and a banner says The order changed in Jira while you were editing, so nothing was saved. Refresh loads the latest and puts your own moves back where they still fit, so the teammate’s change stays. Changes in lists you haven’t touched never block you. See If the order changed in Jira.

Can it keep a list sorted automatically?

No. A sort is a one-off: it puts the list in order once, in your draft, and Save writes that order as Rank. The app works only while someone has it open, with no background jobs, so an issue added or re-ranked later goes wherever Jira puts it until someone sorts the list again. With Priority lanes ticked, new issues wait in Not placed yet at the top of their list, and Place by priority puts each one in its lane. See Priority lanes.

Why don’t priority lanes show in Jira?

Lanes are a way of looking at a list in Issue Order, not something Jira has. Ticking Priority lanes puts each epic’s child issues (and their sub-tasks) in priority order as part of your draft; choose Child issues and epics to put the epics in lanes too. A list of 5 or more issues gets a divider for each priority. Jira gets the order itself, as Rank, when you save, plus a new priority for each issue you drag into another lane. So a list put in lanes shows in Jira in the same order, just without the dividers. Lanes are off each time you open the app.

Does it send notifications?

Reordering changes only Rank, the field a drag on a board changes, so it notifies people no more than reordering on a board does. A new parent or a new priority is an ordinary edit to the issue, made as you, and the app doesn’t turn notifications off for it: the space’s notification scheme decides who hears about it, as when you change the field in Jira. Every change shows in the issue’s History under your name.

What it works with

Does it work in team-managed spaces?

Yes, in team-managed and company-managed spaces alike. A team-managed space keeps parents and children inside itself, both ways, so there Move to… offers only the space’s own epics and doesn’t show Other spaces. In company-managed spaces, Move to… can also put issues under an epic in another company-managed space.

Can I reorder the epics themselves?

Yes. On the Apps page a space’s epics are the top of the outline: drag them, sort them, or use Move up and Move down in a row’s ••• menu. Their order is their Rank, like any issue’s. An epic can’t be moved out of that list. On sites with a level above epics, such as Initiative, you can give an epic another initiative: open its current initiative’s ••• › Reorder child issues and use Move to….

Does it work with sub-tasks?

Yes. Choose Sub-tasks under Show to open them under their issues, or choose Reorder child issues on the issue itself. Drag them into order, sort them, or move them under another issue in the same space. A save ranks them, and the issue’s own sub-task list in Jira follows. Jira keeps sub-tasks in their own space, under a story, task or bug, never directly under an epic.

How many issues can a list have?

Each list shows up to 1,000 issues, in Rank order. Past that, it shows its first 1,000 (with Hide done ticked, its first 1,000 open ones), says so at its end, and Sort is off for it. You can still drag the issues it shows, but not drop issues at its end, because its real end isn’t loaded. See Limits.

Does it work in Jira Service Management, Customer Service Management or Jira Product Discovery?

No. Issue Order is for Jira’s software and business spaces. Reorder child issues doesn’t appear on issues in JSM, Customer Service Management or Jira Product Discovery spaces, and the Apps page doesn’t list those spaces. This only limits where you open it from. A request from one of those spaces that sits under an epic in a software or business space still shows in that epic’s list.

Licensing and purchasing

What does it cost?

Free for teams of 10 or fewer. Above that it’s billed per user, on graduated tiers, through the Atlassian Marketplace on your existing Atlassian invoice; from 11 users, every user is billed. See the pricing calculator.

Do I need a DataPingo account?

No. Billing is Atlassian’s and lands on your existing Atlassian invoice. There is no separate account to create and no payment detail to enter with us.

Is the free tier a trial?

No. Sites with 10 users or fewer are free on an ongoing basis, not for a limited period. From 11 users, every user is billed.

What happens if the subscription lapses?

The app says so as soon as it opens, from either way in, and loads nothing: Issue Order needs an active subscription on this site. Ask your Jira admin to subscribe to Issue Order for Jira on the Atlassian Marketplace. Orders already saved are unaffected: they are Jira’s own Rank.

Privacy and security

Where does my data go?

Nowhere outside Atlassian. The app runs entirely on Atlassian and declares no external domains, so it has no way to send anything elsewhere: it is a Runs on Atlassian app. Nothing reaches a DataPingo server.

What does the app store?

Nothing outside your browser. It has no app storage, no database and no backend, and it runs entirely on Atlassian with no external connections. Your browser keeps a few conveniences: the last space you opened, the Show level, the Hide done and Numbers switches, and which new issues priority lanes have already shown you. While you have unsaved changes it also keeps a copy of them (issue keys, priority names and sort names, never summaries) for up to 14 days. None of it is sent anywhere. See Specs & security.

What permissions does it ask for?

Three, and nothing else: read issues, spaces and their fields; change Rank; and change an issue’s parent and priority. There are no admin permissions and no storage scope. See Permissions required for what each one is used for.

Who makes the changes — me or the app?

You do. Every read and every change is made with your own Jira account, from your browser, so Jira applies your own permissions, exactly as if you had ranked the issues on a board or edited them by hand.

Can the app show someone issues they can’t normally see?

No. It acts as the person using it, so it can only list and change issues that person could already reach. Spaces they can’t browse aren’t listed, and issues hidden from them never load, not even in Move to….

What happens when I uninstall?

Nothing needs deleting in Jira, because the app stores nothing there. Issues stay where the last save put them, in Jira’s own Rank, and saved parents and priorities stay too. Each person’s browser may keep a few small entries until its site data is cleared; see Uninstalling.