Privacy policy: JQL Function Pack for Jira

Last updated: 27 October 2026

This policy covers the Jira Cloud app JQL Function Pack for Jira ("the app"), published by Datadelight ("we"). Questions: privacy@accounts.datadelight.co.

What the app does

The app runs on Atlassian Forge. It adds six functions to Jira's search language (JQL): two that find work items added to or removed from a sprint after it started, two that find work items in sprints starting or ending between two dates, and two that find subtasks or parents of the work items another query matches. When a search uses one of them, Jira asks the app for the answer, and the app replies with plain JQL that lists IDs, for example id in (10001, 10002). Every five minutes the app checks some of its earlier answers, as many as the requests Jira allows it, so each one is checked about every 40 minutes or less often, and updates the ones that have changed.

What the app reads

All reads run as the app, not as the person searching, because Jira shares one answer between everyone who runs the same search. Jira then filters the final results by the searching person's own permissions.

• What you type in the function: the function's name, its operator (in or not in) and its arguments: a sprint name or ID, dates, or a JQL query. The app receives no account ID or other detail about the person searching.
• For the sprint functions: the site's scrum boards (ID and the project each belongs to) and their sprints (ID, name, state, start, end and completion dates, and the board each sprint came from), which field is the Sprint field, and, for the work items in or near the sprint, their ID, project, creation time, current sprints and the history of changes to their Sprint field. From that history it uses only the time of each change and the sprints before and after. The boards and sprints it reads are kept in memory only while one search or one five-minute check runs.
• For the subtask and parent functions: the work items your quoted query matches, with only their ID, or their ID and their parent's ID. When more than 1,000 work items match a subtask function's query, it also reads which of them have subtasks: the ID of each such subtask and of its parent.
• To keep answers current: the answers Jira has saved for the app's functions, with the arguments they were saved for.

What the app changes

Nothing in your work items, sprints, boards or projects. The only thing the app writes to Jira is its own saved answers, described below.

What the app stores

The app has no storage of its own: it keeps nothing in Forge storage.

Jira itself saves the app's answers in your Jira site. For each function and each list of arguments it saves the arguments as they were typed and the answer the app returned, and it shares that answer with everyone who runs the same search. An answer is a list of work item or sprint IDs, or, when a search could not be answered, a message saying why. Such a message can repeat an argument you gave (a sprint name or a date) or the reason Jira gave for rejecting a quoted query. Jira's documentation says it removes saved answers that have not been evaluated for 7 days. These saved answers are part of your Jira site's data, not ours.

What the app sends elsewhere

Nothing. The app talks only to your Jira site and sends no data outside Atlassian. It has no third parties, sub-processors or analytics. Nothing outside Atlassian can call the app either: it has no web address of its own.

Logs

The app writes troubleshooting lines to Atlassian's Forge app logs:

• for each answer: the function's name, its operator, how many work items or sprints it read and matched, and how long it took;
• when an answer fails: the function's name, its operator, whether it was refused, or which Jira request failed and the HTTP status Jira returned, and how long it took;
• for each check (every five minutes, on some of the saved answers): how many saved answers it found, updated, skipped or kept after an error, and how long it took.

The log lines carry no arguments, queries, work item keys, sprint names, account IDs or text from Jira.

Atlassian holds these logs. We can see them in the Atlassian developer console for 30 days. A site administrator can turn off our access to them in Atlassian Administration (Apps › Connected apps › this app › Logs access).

Personal data

The app stores no personal data. The arguments people type are saved by Jira with each answer, as described above, so a quoted query that names a person (for example assignee = …) is kept in your Jira site with that answer.

Your choices and rights

Your Jira site administrator controls the data in your Jira site, including the answers Jira saves for the app. Send questions about the app to privacy@accounts.datadelight.co.

Changes

We will post any change to this policy at this address with a new date.