Version 1.0 · Effective 3 October 2026
This policy explains what data Progress Digest for Jira (Excel Progress Report) (the "app", or Progress Digest) reads, writes, stores and logs, and how it is secured. The app is published on the Atlassian Marketplace by Myriastra Studio ("we", "us"), and is built on Atlassian Forge. The security disclosures are in section 8, Security. The data residency declaration is in section 6.
The app runs entirely on Atlassian's Forge platform, and Atlassian's eligibility check reports the released version as meeting the technical requirements for Atlassian's Runs on Atlassian program (see section 8). We operate no servers, no database and no analytics infrastructure of our own for this app. The app's manifest requests no permission to contact any host outside Atlassian, the app makes no network requests to such a host, and we operate no system that receives your data. The weekly email for scheduled reports is delivered by Jira's own notification service — see section 3.
A report is made when a person presses Generate report on a project's Progress Digest page, or when a scheduled report for that project runs. The app then reads the project's work items on behalf of one person: the person who pressed the button, or, for a scheduled report, the person who turned the schedule on (section 3 says who that is). For each work item it reads the ID, key, summary, work type, status, assignee (account ID and display name), created date, due date and last-updated date. It also reads the project's name and key, and which of the Browse Projects, Create Issues, Create Attachments and Administer Projects permissions that person holds in the project. Because these reads are made on that person's behalf, the work item rows in the report cover only work items that person can see (section 8 describes the one exception).
Using its own identity, the app reads your site's base URL and time zone (to build links and show times), and what it needs to look after the work item that holds the project's reports: the work items in the project whose summary contains [Progress Report], with their standard fields (to find one it made earlier), or the work item you named for reports; the work types the project allows (to create that work item if there is none); and the list of attachments on it (their IDs, file names and the type of account that added each one, to find its own workbooks).
When a person opens or changes the settings or the schedule on the Progress Digest page, the app checks that person's Jira permissions in the project first. When a person presses Generate report, the request is queued and the permission checks are made when the report runs (section 8).
Summaries, work types, status names and display names are used to build the workbook and are not stored by the app (section 4).
This app writes to your Jira site in four ways: it creates one work item to hold the reports (you can point it at an existing work item instead), attaches the generated workbook to that work item, deletes workbooks it previously attached (keeping the 12 most recent), and, for scheduled reports, sends an email through Jira's own notification service to the person who turned the schedule on. It never edits the fields or comments of your work items; the only change it makes to a work item is adding and removing its own workbooks on the report work item.
The work item the app creates is in the project being reported on, with the summary [Progress Report] followed by the project's name, and a work type the project allows (Task, if there is one). The app sets no description, assignee or other field on it.
The workbook has four sheets. It contains the project's name and key, the reporting period and when the workbook was made (in UTC and in your site's time zone); counts by status category (not started, in progress, done, and category not available) with a total and the change since the previous record; lists of work items past their due date and moved to Done, with their key, summary and due date or status; the period's changes (completed, not in the previous record, due date moved, updated date unchanged, no longer in the list) with key and summary, or, for work items no longer in the list, only their ID and a link; and a detail sheet with every work item's key, summary, work type, status, assignee display name, and created, due and updated dates. The workbook is a Jira attachment, so anyone who can see the report work item in Jira can open it, including the rows for work items they could not open themselves (section 8).
The weekly email goes to one person per schedule: the person who turned the schedule on — more precisely, the person who last saved it while it was on. If a project administrator later changes a schedule that someone else turned on, the administrator becomes that person, both for the email and for the reads in section 2. A person receives at most one email per hour band, covering every project whose report they scheduled for that band, and none if no report in that band was completed. Its subject is Progress Digest weekly report. The body gives counts and lists the projects by outcome, up to ten per outcome and fifty in all, each by its project key: a completed report also gives the key of the report work item with a link to it, and a report that was stopped gives the reason, such as a missing permission or a report work item that could not be used — naming the key of the work item you named for reports when that is the one that could not be used. Other outcomes (attached but not fully recorded, a problem before attaching, skipped because another run was in progress, not yet confirmed) are given as a short fixed sentence. The text the app writes does not include work item summaries, the workbook or anyone's name. Jira adds its own header and footer around it, which can show the app's name, the project's name and a link to the report work item with its summary. Jira queues the message and delivers it to the email address on that person's Atlassian account. Pressing Generate report sends no email.
The app stores a compact snapshot of each report inside Atlassian (Forge storage): work item id, status category, due date, assignee account id, and last-updated date — no summaries, no comments, no free text. It keeps the 52 most recent snapshots per project. To run reports, it also stores each project's schedule settings, the account id of the person who saved them, the account id of the person who last ran a report, and records of recent runs. The app does not send data to any server outside Atlassian.
In more detail. The schedule settings are the on/off setting, the weekday, the hour band, when they were saved and the project key the page sends with them, for display. The records of recent runs are kept for 48 hours; each holds the project ID, the account id of the person the run was for, whether a person or a schedule started it, its times and outcome, and, if the run did not finish, the reason. When that reason is an error, its text is kept as it was returned, without shortening. The record of a run that succeeded also holds the key of the report work item and of any other work items that looked like report work items.
For each project the app also keeps: the key of the work item you named for reports, if any, and of the one it last used; the time of the last report and, for each kept snapshot, when it was made, how many work items it covered, in how many parts it is stored and whether a person or a schedule started it; a list of up to 200 workbooks it attached (attachment ID, work item ID, file name and time), so that it removes only its own files; and a record of its latest run, kept until the next run replaces it: its IDs, state, times, what kind of report it was and whether a person or a schedule started it, and the attachment ID, file name and the ID and key of the work item it attached to, or, before attaching, the ID of the work item and the file name it planned to use. To stop the same report or email from being made twice, it keeps short-lived markers that expire after 60 minutes to 48 hours; the markers for a weekly email are keyed by the recipient's account id, and one of them lists the IDs of the projects and requests that email covers. Once per site, it records when the first workbook was attached.
The app does not store work item summaries, display names or email addresses of its own accord. Error text kept as returned (above) could contain such a value if Jira or Forge included one in it. The app does not keep a copy of the workbook; it exists only as the attachment on your report work item.
The app writes to Forge's application log when a report, a scheduled check or an email does not go as planned, and, from time to time, a summary line of its scheduled checks that gives counts and your site's time zone, and no IDs. Two other lines carry no IDs either: once per site, the time the first workbook was attached; and once a day, that time again, with whether any project on the site has a schedule turned on. A line carries IDs (a project ID, a request ID, a work item ID, a snapshot number or an attachment ID), the outcome, counts and the error. Some warnings also carry a key or a file name: the key of a report work item the app remembered but could not find; when asking Jira to send the weekly email fails, the key of the work item the email was sent through, the HTTP status and the error messages Jira returned (up to five, each cut at 200 characters); and when the report work item holds workbooks the app has no record of, up to three of their file names, counting only files named the way the app names its own workbooks.
The app does not write account ids, summaries, display names or email addresses to the log itself; error text returned to us is recorded as we receive it. Forge logs are held on Atlassian's infrastructure and are retained according to Atlassian's platform policy; we read them only to diagnose faults, and we do not copy them anywhere else.
Atlassian's data residency guidance for Forge apps asks each app to define and publish what it treats as in scope and out of scope for data residency. This section is that declaration. It adds no new processing — it restates what sections 2 to 5 already describe.
In scope: everything the app writes to Forge hosted storage, as listed in section 4 — the snapshots with their account ids, the schedule settings, the records of runs (including error text kept as returned), the report work item keys and the list of workbooks. All of it is held exclusively in Forge hosted storage, which Atlassian operates. We operate no storage of our own, so where that data physically sits is determined by the Atlassian platform for the site the app is installed on, under Atlassian's data residency policy rather than under any arrangement of ours.
Read "exclusively" as: this app writes in-scope data to no store other than Forge hosted storage. It does not mean the values in section 5 appear nowhere else on Atlassian's infrastructure — see Platform logs below.
Out of scope:
Your Jira data. The report work item and the workbooks attached to it are part of your Jira site. Jira holds them under its own data residency, not this app.
Data read but not stored. Summaries, work types, status names, display names, the project's name, your site's base URL and time zone are used while a report is made and discarded with it.
Messages between the app's own functions. These carry the project ID, an ID for the request, the account id of the person the report is for, whether a person or a schedule started it, the time, and, for a report over chosen records, which two records; they are passed through Forge's event queue.
Platform logs. The lines described in section 5 sit on Atlassian's logging infrastructure. Their location and retention are managed by Atlassian, not by this app, so we cannot offer a residency commitment over them. If your organisation needs a residency commitment that reaches platform logs, this app cannot give you one — please write to us before you buy rather than after.
Delivered email. Once Jira's notification service has sent the weekly email, the message sits in the recipient's own mailbox with whatever provider they use. We did not hold it, and we cannot recall it.
The app has no sub-processors. It shares data with no third party, and it contains no analytics, advertising or tracking code. It builds the workbook with the open-source ExcelJS library, which runs inside the app on Forge and sends nothing anywhere. This page itself loads a web font from Google Fonts; the rest of the page is served by Cloudflare Pages.
This section is the security policy for Progress Digest. Myriastra Studio is a one-person studio, and this app's security rests on how little the app is able to do, rather than on a formal security program. Most of what follows is a property of the app rather than a promise about us; the commitments we make are under Reporting a vulnerability.
Who is responsible for what. Atlassian provides the platform the app runs on: the infrastructure, tenant isolation, TLS in transit, encryption at rest for Forge storage, and the authentication of the people involved. We are responsible for the app itself: the permissions it asks for, what it does with them, what it writes to logs and storage, its dependencies, and fixing it when something is wrong. Nothing below asks you to take Atlassian's certifications as ours.
The app has no server or endpoint of its own. There is no Myriastra Studio server, database, queue or endpoint anywhere in this app. It exists only as functions running on Atlassian's Forge platform, and its manifest requests no permission to contact any host outside Atlassian. This is why Atlassian's eligibility check reports the app as eligible for Atlassian's Runs on Atlassian program; that is a check on where data can go, not Atlassian vouching for the rest of our code. There is no web trigger and no URL of ours that anyone can call: the app's functions are run only by Atlassian, on a schedule every five minutes, from the app's own queue and from the app's project page. On that page, opening and saving the settings and the schedule checks the person's Jira permission first, and a report request is queued and checked when it runs (below).
We do not receive your credentials. The app does not ask for, receive or store any API token, password or shared secret belonging to you or to anyone on your site. It authenticates to Jira with the identities Atlassian issues to it: its own app identity, and, for the reads described in section 2, access on behalf of a person.
The first time each person opens the report page, Atlassian asks them to grant this app access on their behalf. This is what lets the app read Jira with that person's own permissions (see above). The permission list shown on that screen includes write access, but the app does not write as you: the four writes described above are always made by the app itself.
For a scheduled report, the app uses that access on behalf of the person who turned the schedule on, at the scheduled time, while that person is not using Jira. Turning the schedule off stops this.
The workbook is built with the permissions of the person who enabled or ran the report. Work items that person cannot see are not included.
One exception: the changes sheet compares the report with an earlier record, which may have been made with another person's permissions. For a regular report, that record is the latest scheduled one, made for the person the schedule ran for at the time, or, in a project that has not yet had a scheduled report, the latest record of any kind; a report over two chosen records compares those two records. If a work item was in the earlier record but the person this report is made for cannot see it, the work item can be listed under no longer in the list, with only its ID and a link, and the counts of change are compared against that record too.
If Jira says that person cannot browse the project, no report is made. If Jira does not answer that question, the app goes on building the report and lists the gap in it, but it attaches the workbook only if it can confirm the Create Attachments permission.
The permissions we ask for. The app requests three scopes and no others: read:jira-work, write:jira-work and storage:app. These are declared in the app's manifest, which is the complete list of what the app is able to do. Only read:jira-work is used on behalf of a person. write:jira-work is required by the four writes in section 3: creating the report work item, attaching and deleting workbooks, and asking Jira to send an email. Jira grants that scope more broadly than the app uses it: it would also permit editing, transitioning and deleting work items, and adding comments. The app does none of those things. It changes no field of an existing work item, adds no comments, and deletes only workbooks it attached itself.
Encryption and storage. The app writes your data only to your Jira site and to Forge storage hosted by Atlassian. Encryption at rest and TLS in transit are provided by the Atlassian platform, not by us. We add no encryption of our own, and we operate no storage of our own. The weekly email leaves Atlassian when it is delivered to the recipient's mailbox (section 6).
Who can reach what. Making a report requires that the person can browse the project. Creating the report work item requires Create Issues, and attaching the workbook requires Create Attachments, both checked for that person in the project being reported on. Anyone who can browse the project can open its Progress Digest page, change which work item holds the reports, and turn on a schedule that is off. Once a schedule is on, only the person who turned it on or a project administrator can change it. The outcome of a run is shown only to the person who started it. Anyone who can browse the project can see when each kept record was made and how many work items it covered.
The report work item and its readers. The report work item must be in the project being reported on. If the work item you name is in another project, or the app cannot confirm which project it is in, no report is stored and the result says that the work item could not be used. If a report work item the app chose or created earlier is no longer in the project, the app finds or creates one in the project instead. The workbook is attached by the app, so anyone who can see the report work item can open it, including the rows for work items they could not open themselves (for example, ones under an issue security level). Choose who can see the report work item with that in mind.
The page also shows the time of a project's last report to any person signed in to your site who can use the app, without checking that they can browse that project. Nothing else about the report is shown that way.
The app itself. When the app reads with its own identity, Jira returns only what the app's own permissions allow. Our access is limited to publishing new versions of the app and reading Forge's application log (section 5), through the single Atlassian developer account that owns the app. We have no standing access to your Jira site, and the app has no screen or endpoint through which we can read what it stores; our changes reach your site only as new versions of the app.
How the app is built and released. The app's runtime dependencies are Atlassian's own Forge packages, React and ExcelJS; it bundles no analytics, advertising or tracking library. Every release is built from a version-controlled source tree, and before each deployment we run the project's automated checks (manifest validation, code lint and tests). This is our own practice, not a pipeline that blocks a release by itself. Updates are delivered by Atlassian, not by us. According to Atlassian's documentation, a version that asks for new permissions is held until one of your administrators approves the new scopes. In our experience, a change that adds no scope, such as how an existing scope is used, is not held for that approval.
Reporting a vulnerability. Please write to contact@myriastrastudio.com with security in the subject line, describing what you found and how to reproduce it. If you believe an issue is being actively exploited, say so in the subject line so that it is triaged first. Please test only against a site you control, and please do not access or modify data that is not yours. Please do not put customer data, work item contents or any other confidential material in your report. That mailbox is an ordinary email account outside Atlassian — the property that data stays inside Atlassian belongs to the app at runtime, and it does not extend to an email you send us.
We will acknowledge your report and tell you what we intend to do about it. We work to fix confirmed vulnerabilities within the timeline set by Atlassian's Security Bug Fix Policy, which applies to us as a Marketplace partner. We do not run a bug bounty, do not run continuous scanning or scheduled penetration tests, and cannot offer payment. If we become aware of a security incident affecting this app, we will investigate it and report it to Atlassian as the Marketplace Security Enforcement Policy requires, and we intend to work with Atlassian on containment and a fix, describe it on this page, and contact affected installations wherever we are able to identify them.
What we do not have. So that a procurement team can rule us in or out quickly: Myriastra Studio holds no SOC 2 report and no other third-party security certification, has not completed a CAIQ Lite assessment, and offers no separate data processing agreement. If your organisation requires any of those, this app is not a fit — please write to us before you buy rather than after.
While the app is installed, it keeps the 52 most recent snapshots per project and deletes older ones, and on the report work item it keeps the 12 most recent workbooks it attached and deletes older ones, at most five in one run. The records of recent runs and the markers in section 4 expire after 48 hours or less; the record of the latest run is kept until the next run replaces it.
This clean-up is best effort. The app deletes only workbooks that are in its list of attached workbooks and named the way it names its own. A workbook it has no record of — for example, one attached just before a run was interrupted — is not deleted automatically; if the list ever holds more than 200 entries, the oldest drop off it and those workbooks are no longer deleted; and a workbook whose entry in the list is damaged drops off it in the same way. A workbook whose deletion fails is tried again in a later run. The parts of an older snapshot are deleted once: if that fails, they stay in Forge storage until the app is uninstalled. A report over two chosen records adds and removes no snapshot, but removes old workbooks like any other report. The schedule settings and the other records in section 4 do not expire; the app has no screen for deleting a project's records or a person's account id from them.
Uninstalling the app stops all further processing. According to Atlassian's Forge documentation, the app's Forge storage is then soft deleted and retained for 28 days, and what happens after that follows Atlassian's own data retention and disposal policy, not any action of ours. We cannot delete it sooner, so the data is not erased the instant you uninstall. According to the same documentation, reinstalling the app starts a new installation; it is linked to the old data only if that is requested within 21 days of uninstalling.
The report work item the app created and the workbooks attached to it stay on your Jira site after you uninstall; the app does not remove them. Emails that have already been delivered stay in the recipient's mailbox; we cannot recall or delete them, because we did not hold them.
To stop scheduled reports for a project, turn off Generate a report every week on the project's Progress Digest page and save the schedule; the person who turned it on or a project administrator can do this. The app then queues no new scheduled report for that project. A scheduled report queued before the change can still be made, and the email for it can still be sent. Workbooks already attached stay on the report work item.
If the app's license is inactive, no report is made, by hand or on a schedule, and no weekly email is sent. The page, the settings and the schedule can still be opened and changed.
To stop everything, a Jira administrator can uninstall the app (section 9).
Because the app processes data only inside your own Atlassian site, requests about a specific person's data are usually best served by your Jira administrator, who controls that site. The app has no screen for removing one person's account id from its records, and we have no access to your site, so we cannot remove it for you; after uninstalling, the whole of the app's storage, including those account ids, is left to Atlassian's retention and disposal (section 9). If you would like to contact us about this policy or about a data request, write to contact@myriastrastudio.com. If you are reporting a security vulnerability, please read section 8 first — it tells you what to include and, more importantly, what not to.
If we change how the app handles data, we will update this page and the version and date at the top of it.