Privacy policy: Whole Number Field for Jira

Last updated: 28 October 2026

This policy covers the Jira Cloud app Whole Number Field 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 a custom field type, Whole number, which accepts whole numbers only and shows them without a thousands separator unless a Jira administrator turns one on for a field context. It also adds an administration page that copies values from an existing Jira number field into a Whole number field.

The field

The values of Whole number fields are stored by Jira in your Jira site, like any other custom field. The rules that refuse decimals and show the value are run by Jira itself, inside your site. The app's own code does not run when someone views or edits the field, and the app does not receive those values.

A field context's settings (a minimum, a maximum and a thousands separator) are also stored by Jira in your site, against that field context.

What the copy page reads

When a Jira administrator uses the copy page, the app reads, as that person:

• the list of fields on the site (each field's ID, name and type), to offer the number fields and Whole number fields to choose from;
• the work items that match the person's query and have a value in the chosen number field, with only their ID, their key and the values of the two chosen fields. It does not ask for summaries, descriptions, comments, attachments or other fields.

What the copy page changes

When the person confirms a copy, the app sets the chosen Whole number field, as the app, on the work items whose number field holds a whole number and whose Whole number field is empty. It changes nothing else. Jira shows the app as the one who made these changes.

What the app stores

Nothing. The app has no storage of its own. The copy page's report (counts, and the keys and values of work items it did not copy) is shown to the person on the page and is not kept.

What the app sends elsewhere

The app uses Atlassian Forge and your Jira site. Its assessed manifest declares no external integrations or analytics services; the app code makes no calls to an external analytics service.

These app-level observations do not establish the platform’s contractual role or an authorised subprocessor list. Platform legal entities, contractual chain, processing locations, transfers and retention remain to be verified before completing an agreement, as described in processing annex C.

Logs

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

• for each page of up to 100 work items read by the copy page: whether it was a preview or a copy, how many work items were read and how many were copied;
• when a request fails: which of the page's actions failed and the HTTP status Jira returned.

The log lines carry no query, work item keys, field values, 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.

Your choices and rights

Your Jira site administrator controls the data in your Jira site, including the values of Whole number fields. 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.