Admin guide
The Jira permissions that decide who can reorder, where the app appears, and licensing.
The app acts as you
Issue Order for Jira makes every read and every change with the signed-in person’s own Jira account, from their browser. It has no service account and no elevated identity: if Jira would refuse you, it refuses the app. So there is nothing to configure. Your Jira permissions already decide what each person can do, and two people opening the same epic can see different issues and be allowed different things.
Jira permissions
The app checks these for each space as its issues load, and Jira checks again when you save.
| To | What you need | Without it |
|---|---|---|
| See a space and its issues | Permission to browse the space. Issue security applies as anywhere in Jira. | The space isn’t listed on the Apps page, and issues you can’t see never load, not even in Move to…. |
| Reorder issues: drag, Sort…, Put in lanes, Move up and the rest | Schedule issues and Edit issues in the issue’s space, the pair Jira’s own ranking needs | Read-only, with a banner. A drag says You can’t reorder issues in Shop. It needs the Schedule issues and Edit issues permissions. and nothing moves. |
| Give an issue another epic or parent | Edit issues, plus Schedule issues to place it in its new list | The issue stays put, with the reason, such as You can’t change SHOP-12’s parent: it needs the Edit issues permission in Shop. |
| Change a priority by dragging into another lane | The same as reordering, since the drag reorders too | Nothing moves. |
The read-only banner
When you lack either permission in a space whose issues are on screen, a banner names it: You can see Shop but can’t reorder there. It needs the Schedule issues and Edit issues permissions. Everything stays readable, and changes that involve that space are refused with the reason.
If the check itself fails, the app doesn’t assume no. It lets you work, and Jira gives the real answer at save: anything refused is named and stays in your draft, and the rest is saved.
Where to grant them. In a company-managed space, from the space’s permission scheme. In a team-managed space, the person’s role in the space decides. Newer Jira screens may say “work items” where these names say “issues”.
Nothing to configure
There is no settings screen, no admin page and no app data to manage. A Jira site admin installs the app once for the whole site, because Forge apps can’t be installed per space (see Installation). After that, everyone can open it. The view choices (Show, Hide done and Numbers) and the last space opened are kept in the browser, not in Jira, so they never change anyone else’s view. Priority lanes starts off each time the app opens.
Where the app appears
- Issue Order for Jira under Apps in Jira’s sidebar. It lists the software and business spaces you can browse, each marked with its kind, such as Software · Company-managed.
- Reorder child issues in the ••• menu of any issue in a software or business space. It opens the same organizer in a pop-up, on that issue.
It isn’t offered in Jira Service Management, Customer Service Management or Jira Product Discovery spaces: there the ••• action isn’t shown, and the Apps page doesn’t list them. Where to open it shows both ways in.
Team-managed and company-managed spaces
Issue Order works in both. Where they differ, the rule is Jira’s, and the app checks it before a move is staged.
| Company-managed | Team-managed | |
|---|---|---|
| Reorder an epic’s child issues | Yes. Jira’s own child list can’t be dragged into order here: this is the gap the app fills. | Yes |
| Use an epic in another space | Yes, between company-managed spaces, with Other spaces in Move to…. Those issues show in their own space under Under epics in other spaces. | No, in either direction. Move to… says Space is team-managed, so these issues can only go under its own epics. |
| Who can reorder | The space’s permission scheme | The person’s role in the space |
In both, a parent is exactly one level up, and sub-tasks stay in their own space. Every rule and its message is under Limits.
Jira’s Rank field
A save writes Jira’s own Rank, the field the epic’s child list, boards and backlogs sort by. The app finds the site’s Rank field by itself, and almost every Jira Cloud site has one. Two things stop reordering; the outline still opens, but Save changes stays unavailable:
- No Rank field. Lists show issues oldest first, with the banner This Jira site has no Rank field, so issues can be seen here but not reordered.
- Jira won’t rank for this person. The app asks Jira when it opens, and again before saving, with a rank request that changes nothing. If Jira refuses, the banner reads Jira’s ranking isn’t available to you on this site, so issues can be seen here but not reordered.
If you see either, write to support@datapingo.com with the exact message.
Licensing
Issue Order is free for teams of 10 or fewer users. 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. Prices are on the Marketplace listing. A site admin starts a trial or subscribes from the app’s page on the Marketplace.
The license is checked every time the app opens. If the site’s subscription isn’t active, both ways in show only Issue Order needs an active subscription on this site. Ask your Jira admin to subscribe to Issue Order for Jira on the Atlassian Marketplace. In the pop-up, Close closes it. Orders already saved are unaffected: they are Jira’s own Rank.
Uninstalling
A site admin uninstalls the app from Manage apps, under Settings → Apps in Jira. There is nothing to export or clean up. Everything the app saved is Jira’s own (Rank, parents and priorities), so every issue stays where the last save put it.
The only traces are in each person’s browser: their view switches and last space, the priority lanes’ notes, and any unsaved changes the safety net kept (issue keys, priority names and sort names, never summaries). None of it is ever sent anywhere. What it stores lists each item.