Short version: the app runs on Atlassian Forge. Your attachments and work items stay in Jira. The app stores only each user’s settings and the date of its first use, and sends nothing to any other service.
Architecture
| Component | Where it runs | Operated by |
|---|---|---|
| User interface | The user’s browser, in a sandboxed frame inside Jira | Served by Atlassian |
| App functions | Atlassian Forge | Atlassian |
| Jira REST API and attachments | Atlassian Cloud | Atlassian |
| Servers of Green Builds Software | Do not exist |
What the app can access
A Jira administrator approves these permissions when installing the app.
| Permission | What the app uses it for |
|---|---|
read:jira-work |
Read work items and their attachments |
write:jira-work |
Delete attachments when a user asks for it |
read:jira-user |
Show the name and avatar of the person who uploaded a file |
write:user.property:jira |
Remember each user’s settings, such as column widths |
storage:app |
Remember when the app was first used on your site |
Requests are made on behalf of the signed-in user. Jira applies that user’s permissions, so nobody sees or deletes an attachment they could not see or delete in Jira itself.
What the app stores
| Data | Where |
|---|---|
| A user’s column and download settings | A property of the user in Jira |
| The date the app was first used on your site | App storage on Atlassian Forge |
The app does not store file names, file contents or work item texts.
Usage and error logs
To find and fix errors, the app writes a small number of entries to its log on Atlassian Forge:
- that the app was opened,
- that a search has finished, with the number of work items and attachments it loaded and how long it took,
- errors, with their technical details.
The entries contain no user ID and no site ID, and no file names, file contents or work item texts. We can read these logs in Atlassian’s developer console, where Atlassian shows which installation an entry came from. Atlassian keeps app logs only for a limited time, currently up to 60 days, and they are not passed on to anyone.
Reporting a vulnerability
Use our vulnerability report form, or write to support@green-builds.com. How we handle reports is described in the Trust Center.