FieldPilot is a Forge app for Jira Cloud. It fills default field values by project and issue type. This notice describes what the app stores and what it does not do. It is the text to host and link from the Marketplace listing (see `COMMERCIAL.md`).
简体中文摘要：FieldPilot 只在客户的 Atlassian 站点内运行。规则、诊断和许可证快照存在 Forge 存储里，不会发到 Atlassian 以外的服务器。应用没有远程后端，也没有分析上报。
The app runs on Atlassian Forge (Runs on Atlassian eligibility is described in `README.md`). There is no vendor-operated server, no `remotes` entry, and no `permissions.external` fetch. The app does not send analytics.
| Data | Why | Example |
|---|---|---|
| Field rules | So admins can reuse defaults | Project key, issue type name, priority id, label strings, description template, assignee account id, due-date offset, component and version ids, custom field id / kind / value |
| Last UIM registration summary | Show whether registration succeeded | Timestamp, rule id, success or error text |
| License snapshot | Fallback when a trigger has no `context.license` | `{ active: true/false, at }` only |
| Apply diagnostics (last 100) | Admin troubleshooting | Time, issue key, rule ids, field names that were applied or skipped, error message |
Rules stay until an admin deletes them or the app is uninstalled. Diagnostics stay until an admin clears them or the app is uninstalled. Uninstall removes Forge app storage for that installation.
Using the app's asApp identity, FieldPilot reads projects, issue types, priorities, components, versions, label suggestions, users matching an admin's search, and the issue that was just created. It writes an issue only to fill fields that are still empty and allowed on the edit screen.
The admin page calls Jira as the current user once per resolver request to check the global `ADMINISTER` permission. That response is not stored.
Assignee values stored on a rule are Atlassian account ids, not email addresses. The account id is whatever the admin picked in the user picker.
These are the classic scopes required together by `jira:uiModifications`, plus Forge storage. Comments in `manifest.yml` match this table.
| Scope | Use |
|---|---|
| `read:jira-user` | Assignee account id on the create dialog; user search in the admin page |
| `read:jira-work` | Projects, issue types, fields, and the created issue |
| `write:jira-work` | UI Modifications `setValue`; post-create update of empty fields |
| `manage:jira-configuration` | Create and delete this app's UI modification records |
| `manage:jira-project` | Required with the UI Modifications scope group (screen tabs). The app does not change project settings |
| `storage:app` | Forge KVS for the table above |
Use the support channel published on the Atlassian Marketplace listing. Until that listing exists, the installing site's Jira administrator is the operator of the rules stored for that site.