CloudBrief

UX & Product Design Insights Dashboard for Jira

Understand your UX & Product Design investment through read-only executive metrics and Design planning insights.

• View on Atlassian Marketplace

CloudBrief Hierarchy Change Preview for Jira

Preview proposed Jira hierarchy changes, identify parent-child relationships that would break, and review cases requiring an administrator decision—all without changing Jira.

How Hierarchy Change Preview Works

Jira permissions remain in effect throughout the scan. Hidden or inaccessible work is not treated as proof that a proposed change is safe. Keep the page open while larger scans run. No Jira changes are performed.

Strategy & Investment StorytellingComing soon for JiraFrom your data in Jira to the story behind your organization’s priorities, investments, and tradeoffs.Turn recorded Jira work and changes into department stories and leadership updates. Explore strategy options and investment tradeoffs supported by linked Jira evidence, then export selected findings to PowerPoint, Excel or CSV.Start with one project and choose the organizational functions to include. Findings reflect the work and history available to your Jira account. Work-item counts do not measure staffing, spending or financial returns.

Privacy Policy for CloudBrief Jira Apps

UX & Product Design Insights Dashboard for Jira
*Effective date: September 22, 2026CloudBrief is a product of Alyssa Arrigo LLC. This policy explains how the
CloudBrief Jira app accesses, processes, stores, and protects information.1. Information the app processesThe app processes Jira information that the signed-in user is already permitted
to access. Depending on the customer's Jira configuration and the reporting
selection, this may include projects, boards, sprints, releases or versions,
fields, statuses, issue types, labels, work items, work-item summaries,
hierarchy links, and assignee identifiers.The app may temporarily process Atlassian account identifiers and display names
to calculate aggregate contributor and function metrics. It does not persist
those user identifiers or profiles in app storage.2. How the information is usedThe app uses visible Jira information to create read-only executive and manager
dashboards, historical comparisons, UX and Product Design evidence metrics,
linked-Epic evidence, Design Readiness worklists, and onboarding suggestions.The app does not use Jira information for advertising, sell it, score individual
productivity, or infer undocumented work. The current app does not create,
change, or delete Jira issues, projects, boards, sprints, releases, workflows,
labels, roles, or fields.3. Information storedThe app stores only installation-wide configuration decisions needed to operate
the dashboards, such as administrator-approved mapping names, mapping targets,
mapping status, and approval time. This configuration is stored using
Atlassian-hosted Forge storage.The app does not persist Jira issue content, user profiles, Atlassian account
identifiers, salaries, timesheets, payment-card data, or narrative prompts. It
does not cache personal data for longer than 24 hours.4. Hosting and disclosureThe app runs on Atlassian Forge. Jira information and app configuration are
processed within Atlassian's platform and are subject to Atlassian's applicable
security, data-residency, retention, and subprocessors practices. CloudBrief
does not send Jira information to an external application server, advertising
network, data broker, or analytics provider.This public information page is hosted by Carrd. The Jira app does not send Jira
information to Carrd. Carrd may process ordinary website request information
under its own privacy policy when someone visits this page.5. Retention and deletionAdministrator-approved mapping configuration remains available while the app is
installed unless it is replaced or removed. When the app is uninstalled,
Atlassian handles Forge-hosted storage according to its app-data lifecycle and
retention policies.An authorized customer administrator may contact CloudBrief to ask questions or
request assistance concerning stored app configuration.6. Access controls and securityJira reads are performed in the context of the signed-in user. Jira permissions
and issue-security rules continue to control which records the user and the app
can access. Installation-wide mapping approvals require Jira administrator
permission.CloudBrief uses the security controls provided by Atlassian Forge and minimizes
the permissions and stored information required for the app to work.7. Your choices and rightsCustomers control Jira permissions, the information recorded in Jira, approved
app mappings, and whether the app remains installed. Depending on applicable
law, individuals may have rights concerning personal information. Because the
app does not persist user profiles or account identifiers, requests involving
Jira account information should generally be directed to the customer's Jira
administrator or Atlassian. Privacy questions about CloudBrief may be sent to
the address below.8. Changes to this policyThis policy may be updated when the app's features or data practices change. The
effective date above will be revised when a material update is published.9. ContactFor privacy or support questions, contact [email protected].Strategy & Investment StorytellingProduct-specific privacy information · October 4, 2026This section applies to Strategy & Investment Storytelling. The dashboard policy above describes UX & Product Design Insights Dashboard for Jira.Information and purpose
The app reads work metadata and available change history for one selected Jira project using the signed-in user’s access. This includes project and work-item identifiers, work types, relationships, status, labels, components, supported department fields and recorded changes to status, parent, due date and release assignments. It prepares evidence-based stories and conditional strategy options. It does not deliberately request descriptions, comments or attachments for analysis, modify Jira work items or send Jira data to an external AI provider.Saved information
Department names, grouping identifiers and selected epic keys are stored in Atlassian Forge, scoped to the account, site and project. Account and site identifiers are processed to separate settings; hashing a storage key does not make its configuration anonymous. A privacy inventory stores the account identifier, oldest collection timestamp, references to saved setups, reporting dates and pending deletion status. Scheduled reporting sends account identifiers and collection timestamps to Atlassian and processes its account-deletion instructions. The current app does not create browser backups and attempts to remove accessible legacy backups when opened. Jira histories and generated stories are not saved by the configuration service. Settings have no automatic app-defined expiry.Downloads and deletion
Selected stories can be downloaded as PowerPoint, Excel or CSV. The inactive-subscription screen also permits a JSON download of saved setup. Downloads are created in the browser and customers control their copies.Clear saved department setup replaces choices with an empty settings record. Delete my saved setup removes the account/project record and its privacy-inventory reference. A Jira administrator can confirm Reset app setup to remove saved department selections, epic assignments and privacy inventory for all users and projects in this app installation. Saving pauses during reset and resumes after completion is verified. Interrupted resets can be retried. Non-personal control records remain to coordinate resets and privacy reporting. Legacy backups in other browsers and downloaded files require separate removal. These actions do not delete source Jira records; Atlassian’s platform retention is separate from active app-record deletion.Hosting and support
The app uses Atlassian Forge and the user’s browser, with no external CloudBrief application server. Jira information is not sent to Carrd. Support uses the same CloudBrief Google Workspace/Gmail mailbox arrangement as our other apps. Contact [email protected] for return or deletion assistance, or [email protected] for privacy questions. We verify requester authority and the relevant installation before confirming completed requests. Do not email credentials or complete Jira datasets.Your choices
Customers control Jira permissions, project selection, department mappings and downloaded files. Depending on applicable law, individuals may have rights concerning personal information. Contact CloudBrief about saved app configuration; contact your Jira administrator or Atlassian about source Jira account records. We will update this section when material processing practices change.

Support

Email [email protected] for installation, authorization, mapping, dashboard, or privacy questions. Support is monitored Monday through Friday, 9:00 a.m. to 5:00 p.m. Eastern Time, excluding United States federal holidays.Initial-response targets are one business day for a suspected security incident or app-wide outage, two business days for installation or incorrect-result questions, and five business days for general questions and feature requests. These are response targets, not guaranteed resolution times.Do not send passwords, API tokens, payment-card information, health information, or confidential Jira content by email.

Security Summary

UX & Product Design Insights Dashboard for JiraThe app runs on Atlassian Forge, reads Jira in the context of the signed-in user, respects Jira permissions and issue security, and performs no Jira writes. It has no external runtime server or data egress. Administrator-approved mapping configuration is stored in Atlassian-hosted Forge storage. Jira issue content and Atlassian account identifiers are not persisted by CloudBrief.Potential security vulnerabilities may be reported privately to [email protected] with the subject “Security report: CloudBrief Jira app.”Strategy & Investment StorytellingRead-only Jira access respects the signed-in user’s permissions. Account, site and project context separates saved department settings in Atlassian Forge. Saved account identifiers and collection timestamps support scheduled privacy reporting to Atlassian and account-related deletion. The current app does not create browser backups. Jira administrators can reset this app’s saved setups; saving resumes after verified completion. Analysis runs in the browser; generated stories and Jira histories are not saved by the configuration service. No external AI provider or CloudBrief application server is used. See this product’s privacy section for storage and deletion details.

End User Terms

The Marketplace version uses Atlassian’s standard end-user agreement. The applicable agreement is presented through Atlassian during Marketplace installation.

Data Processing Addendum

The September 20, 2026 CloudBrief Data Processing Addendum includes product-specific schedules for UX & Product Design Insights Dashboard for Jira and CloudBrief Hierarchy Change Preview.View the CloudBrief Data Processing AddendumFor Strategy & Investment Storytelling, read the base DPA together with the October 4, 2026 Service C supplement. The supplement applies when incorporated and accepted under the applicable agreement.View the Strategy & Investment Storytelling DPA Supplement

Strategy & Investment Storytelling — Getting started1. Load a project
Open Strategy & Investment Storytelling from Jira Apps. In Setup, enter a Jira project key, such as SCRUM, and select Analyze your organization for departments. The app reads one project at a time using your Jira access.2. Choose your organizational functions
Confirm the groupings found in your Jira data, or select functions such as Engineering, Product Design, Product Management and Quality Engineering. Use Add another function for a different name, then Include selected functions. These choices do not change Jira labels or records.3. Connect work to departments
In Departments, open Allocate epics for a function, choose the epics it contributes to, and Save allocation. Selecting a function alone does not allocate every epic. Work can contribute to more than one department; do not add overlapping department totals together. Unmatched epics remain under Not allocated to any department. You can add or remove departments later.4. Analyze the story
Use Analyze department stories or the analysis control in Organization Story to read recorded Jira changes. Review what changed, why it may matter, a strategy to consider and its investment tradeoff. Expand Behind the Numbers and follow Jira work links to inspect the evidence. Department stories use your current mappings; they do not establish historical ownership.5. Choose a review period
Use the review-period controls to select your dates and apply the period. Dates use your Jira time zone when available, otherwise your browser time zone. Available history returns to the full history loaded by the app. Review the coverage notes before drawing conclusions. An empty result can mean no relevant recorded changes were found for the selected work and dates.6. Prepare a leadership update
Open Leadership Review to review the implications, possible value and decisions to consider. These are conditional prompts based on recorded changes. They do not establish causes, calculate spending, measure staffing or guarantee business outcomes.7. Export selected findings
Select Export Results, choose the findings to include, and download PowerPoint, Excel or CSV. Export becomes available after recorded changes have been loaded. Your downloaded files remain under your control; deleting app settings does not delete them.Saved setup and deletion
Department choices are personal to your Jira account, site and project. They are saved in Atlassian Forge. Check the save message: if saving fails, retry before leaving the page. The current app does not create browser backups. Jira history and generated stories are not saved by the configuration service.Clear saved department setup removes your choices but leaves an empty account/project record. Delete my saved setup deletes that record and its privacy-inventory reference. Legacy backups from older versions are removed when accessible in the current browser; open the updated app in other browsers or remove their local browser data to clear older copies. Source Jira work and downloaded reports are unaffected.Jira administrators can use Reset app setup and confirm removal of this app’s department selections and epic assignments for all users and projects on the site. The app removes saved setups and privacy inventory automatically in batches. Saving pauses during reset and resumes after completion is verified. If reset is interrupted, retry it to finish. This does not change Jira projects, issues, other apps or downloaded reports.Coverage and troubleshooting
The app uses accessible records in one project. Direct-child completion counts exclude subtasks and work in other projects. Deleted, moved or inaccessible work may be missing. Large projects and history retrieval have limits; read the coverage messages and retry failed requests before relying on a result. Reloading a project clears the current analysis, so run the analysis again. No external AI service is used, and Jira records are not modified.Support: [email protected]
Security: [email protected]
Do not send passwords, tokens or complete Jira datasets with a support request. Include the screen or action, the error message and a redacted screenshot if useful.