Privacy policy: Bulk Change Issue Links for Jira

Last updated: 23 October 2026

This policy covers the Jira Cloud app Bulk Change Issue Links for Jira ("the app"), published by Datadelight ("we"). Questions: privacy@datadelight.co.

What the app does

The app runs on Atlassian Forge. It finds the issue links on the work items a JQL query matches, shows a preview of changing their link type, and, when you confirm, changes them in the background. It keeps a record of each run so the run can be followed and undone.

What the app reads

• As you, when you use its page: the work items your query matches, with only their links (for each link: its ID, its type, and the ID and key of the work item at each end). It does not ask for summaries, descriptions, comments, attachments or other fields.
• As you: the site's link types, and whether you may browse, and link, each work item at either end of the links you selected, and whether you are a Jira administrator.
• As the app, during a run or an undo: each selected link, and the links of the work item at its outward end, to find the link it has just made.

What the app changes

During a run, for each selected link, the app adds a link of the new type between the same two work items and removes the old link. An undo does the reverse. It changes nothing else. These changes run as the app, so Jira shows the app as the one who made them. The app only changes links on work items that you, the person who started the run, may browse and link, and an undo only those that the person undoing may browse and link.

What the app stores

The app keeps a record of each run in the app's Forge storage:

• the query, the link type changed to, the time, and the Atlassian account ID of the person who made the preview and started the run (and of the person who undid it);
• the project key, for runs made from a project page;
• for each link: the link's ID, the ID and key of the work item at each end, the old and new link type, and the outcome, with the reason when a link was skipped or failed. A reason can quote up to 160 characters of the message Jira returned;
• for an undo, the IDs of the work items the person undoing may browse and link.

Each record expires 90 days after it was last written. After that the run no longer appears in the app's history and cannot be undone.

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.

Logs

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

• when a run or an undo starts: the run's ID and how many links it will change, skip or undo;
• for each batch of up to 100 links: the run's ID, whether it was a run or an undo, the batch number and whether it finished;
• when a request fails unexpectedly: which of the page's actions failed and the HTTP status Jira returned.

The log lines carry no query, work item keys, 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 only personal data the app stores is the Atlassian account ID of the people who start or undo a run, kept with the run's record as described above.

Your choices and rights

Your Jira site administrator controls the data in your Jira site. Send questions or requests about the app's run records to privacy@datadelight.co.

Changes

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