Specs & security

Technical specifications

System requirements

• A Jira Cloud site with software or business spaces
• A modern web browser, with an internet connection
• Jira’s Rank field, which almost every Jira Cloud site has
• To change an order: the Schedule issues and Edit issues permissions in that space, which Jira’s own ranking needs

Permissions required

Three scopes, and no others:

• read:jira-work — read the spaces you can browse and their issue types; issues (summary, type, status, priority, due date, created, parent and sub-tasks) and their Rank; the Rank field’s id; the site’s issue types; and your own Schedule issues and Edit issues permissions. For Priority lanes and sorting by priority, the site’s priority order, read from a few issues’ edit screens (or Jira’s own priority list, where the site allows it). For Move to…, search for epics and issues. For Sort…, one issue’s edit screen per space and issue type, to see which of the space’s fields can be sorted by and a choice field’s options in order, and the values of the field a sort uses.
• write:issue:jira-software — change Rank. This is the only scope Jira’s rank endpoint accepts.
• write:jira-work — change an issue’s parent (Move to…, or a drop onto another epic or issue) and its priority (a drag into another priority lane).

Privacy & security

• Data privacy: DataPingo Privacy Policy
• Security: DataPingo Security Policy
• Hosting: Atlassian Forge. Issue Order is one screen that Jira shows in a frame; it has no backend function, no triggers and no scheduled or background jobs, so nothing of it runs while nobody has it open.
• Data storage: None outside your browser. Unsaved changes live in your open tab, with a safety-net copy in your browser, and the order itself lives in Jira’s Rank.
• Browser storage: Your view switches, the last space you opened, the priority lanes’ note of which new issues you’ve seen, and a safety-net copy of unsaved changes (issue keys, priority names and sort names, never summaries) are kept in your browser’s local storage. They never leave that browser; the drafts and notes are filed under your Atlassian account ID so two people sharing a browser don’t see each other’s. A kept draft is dropped after 14 days; the lane notes and view switches stay until the browser’s site data is cleared. What it stores lists each one.
• Personal data: The only personal data the app uses is your own Atlassian account ID, from Forge, as part of the names under which your browser keeps your safety net and lane notes, so they stay separate from anyone else using the same browser. It never leaves your browser. The app reads the issue fields it shows and sorts by, and none that hold people: no assignee, reporter or other people fields, no descriptions and no comments. It reads them live from Jira as you and shows them only to you. Jira’s space details also include the space lead, which the app ignores.
• Authentication: Every call to Jira is made as you, through Forge’s requestJira in your browser. The app never acts as itself, uses no impersonation, and holds no secrets, API keys or personal access tokens.
• Egress: None. No external domains are declared, nothing is sent outside Atlassian, and the app has no web triggers or API of its own for anything outside Jira to call.
• Data residency: There is no end-user data in scope, because nothing is stored.
• Logs: The app keeps no logs. Its few warnings go only to your own browser’s console, and if its screen ever fails, you see the error on screen and in that console.
• Customer information: We receive customer details only through the Atlassian Marketplace. We do not sell, distribute or share that information.
• Reporting a security issue: security@datapingo.com
• Uninstalling: Nothing to clean up. Issues stay exactly where you put them, because the order is Jira’s own Rank, not the app’s. See the Admin guide.