Security Policy

Security Policy

Architecture

Multi Project Picker Fields for Jira is built on Atlassian Forge, Atlassian's serverless app runtime. The app runs entirely within Atlassian's infrastructure. There are no external servers, no third-party services, and no data routing outside of your Atlassian site.

Data handling

  • Project data is read via the Jira API using the permissions of the currently logged-in user. Only projects the user already has access to are returned.

  • Field configuration (project type and category filters) is stored in Forge KV Storage, scoped to the app, and never leaves Atlassian infrastructure.

  • No end-user data is stored by the app beyond what Jira stores natively as the custom field value.

  • No data is sent to any third-party service or external endpoint.

Permissions

The app requests the minimum permissions required:

  • read:jira-work search for projects and fetch project details to populate the picker

  • storage:app store per-field configuration in Forge KV Storage

The app has no write permissions to Jira data. It cannot create, modify, or delete issues, projects, or any other Jira objects.

User context

All Jira API calls use asUser(), meaning they execute with the permissions of the logged-in user. The app cannot access any data the user could not access directly in Jira.

Reporting a security issue

If you discover a security vulnerability, submit a ticket. We will acknowledge within 2 business days and aim to resolve confirmed issues within 14 days.