Reference
Permissions, data, licensing
What the app stores
- The HubSpot key — in Forge secret storage for your site, never shown again.
- Which HubSpot record IDs are linked to which issue — numbers only, no names or amounts.
- Settings and the last recompute — portal ID, currency, ARR property, time and count of the last run.
- The three field values — written into Jira like any other field.
The app stores no personal data: no Atlassian account IDs, no contacts, no deal or company names.
What it reads
- From HubSpot: companies, deals, tickets, their associations and pipelines, with the key you provided.
- From Jira: your permissions on the issue (to see and to edit), the app's own fields, and issue search for its own fields.
Where data goes
Requests go from Atlassian's Forge platform directly to api.hubapi.com. There is no YTI server in between and nothing is sent to YTI Digital. HubSpot data shown in the panel is read live and not kept.
Jira scopes
| Scope | Used for |
|---|---|
read:jira-work | Checking issue permissions and searching for issues that carry the app's fields |
write:jira-work | Setting the values of the app's own read-only fields |
storage:app | Keeping links, settings and the HubSpot key |
Who sees what
- Anyone who can see an issue sees its panel and fields, including deal amounts and customer names read with the admin's key.
- Changing links needs permission to edit the issue. Settings are for Jira administrators only.
Licensing
Free for up to 10 users; above that, billed per user by Atlassian through the Marketplace. With an inactive licence the panel stays readable, but links and settings cannot be changed.
Details: Privacy Policy · Terms of Service.