Promote to Project privacy notice
Effective 8 October 2026. Publisher: Taylor Apps. Contact: support@pulse-apps.co.uk.
What the app does
Promote to Project lets an authorised Jira user copy selected Jira Service Management tickets into an allowed destination Jira project. It copies summaries, descriptions and accessible attachments, assigns the chosen issue type, Epic, component and workflow status, and links new tasks to their originals. Source and destination projects are within the same Jira Cloud site. Each installed site has separate configuration and records.
Information processed
The app reads Jira project and issue information, field and workflow metadata, attachment filenames and content, issue links, account identifiers and permissions to carry out the requested operation. Jira content and attachments may contain personal or confidential information supplied by your organisation.
The app stores installation settings, the initiating user's Jira account identifier, issue and project identifiers, selected destination settings, run timestamps, result messages, attachment metadata and processing checkpoints in Atlassian Forge storage. Additional administrator-configured field defaults are also stored. Records support run history, retry recovery, permission checks and duplicate prevention. Account identifiers and processing records may be retained for longer than 24 hours.
Attachment file content passes through the app's worker while being copied to Jira. The app does not persist attachment binaries in its Forge key-value storage. Copies remain Jira attachments in the destination project. Descriptions and summaries are copied to the new Jira issue.
Hosting and access
The app runs on Atlassian Forge and uses Jira APIs and Atlassian-hosted storage. The current app has no external application backend or declared external data egress, advertising integrations or marketing analytics. Atlassian hosts the app and processes data under its applicable service terms. The app requests only the Jira and Forge permissions described on its installation page.
Operations use the initiating Jira user's access. App administrators control which projects can be used. Run history is accessible to the initiating user, subject to continued Jira issue access. Technical developer access to diagnostic information and app storage is governed by Atlassian's developer controls. Do not submit sensitive issue content in support requests unless necessary and agreed.
Copies and visibility
Copied content follows the destination project's Jira permissions. Those permissions may differ from the source service project. Users must review destination access before promoting tickets, especially when attachments contain personal or internal information. Removing the app does not remove tickets or attachments it created in Jira.
Retention and requests
The current app retains processing records to maintain history, recovery checkpoints and duplicate protection; it does not automatically expire them. Jira ticket and attachment retention is controlled by the organisation operating Jira. Forge storage retention after uninstall is governed by Atlassian's current platform policy. Do not treat uninstalling the app as a way to delete copied Jira content.
Contact your Jira administrator about copied ticket content, project access or Jira deletion requests. Contact Taylor Apps at support@pulse-apps.co.uk for questions about app records, retention or personal information. Applicable requests require verification and may involve the site's Jira administrator. Support requests sent outside the app are processed through the chosen support channel, separately from app storage.
Changes
This notice will be updated when the app's processing, hosting, support arrangements or retention behaviour changes. You can contact Taylor Apps at support@pulse-apps.co.uk about this notice.