Frequently Asked Questions

Quick answers to common questions about Simple Risk Register for Jira.

General

What is Simple Risk Register?

Simple Risk Register is a Jira Cloud app that helps you manage project risks with a visual heatmap, detailed table view, and Jira issue integration. It runs entirely within Jira, so your risk data stays where your work happens.

How much does it cost?

Check the Atlassian Marketplace listing for current pricing. The app offers a free trial so you can evaluate it before purchasing.

Which Jira versions are supported?

Simple Risk Register supports Jira Cloud only. It does not work with Jira Server or Jira Data Center.

Who is this app for?

The app is designed for:

• Project Managers
• Scrum Masters
• Product Owners
• Delivery Managers
• Any team that needs lightweight risk tracking in Jira

Data and storage

Is risk data shared across Jira projects?

No. Each Jira project has its own isolated risk register. Risks created in one project are not visible in other projects.

Where is my risk data stored?

Risk data is stored in Atlassian Forge Storage, which is part of Atlassian’s Cloud infrastructure. Data remains within your Jira tenant and is not sent to external servers.

Can I back up my risk data?

Yes. Use the Export feature to download your risk register as a CSV file. We recommend regular exports for backup purposes.

What happens to my data if I uninstall the app?

When you uninstall the app, your risk data is retained in Forge Storage for a period per Atlassian’s retention policy, then permanently deleted. Export your risks before uninstalling if you want to preserve the data.

Does the app send data to third-party services?

No. The app operates entirely within Atlassian’s infrastructure. It does not use external analytics, tracking, or third-party services for core functionality.

Risk management

How is risk score calculated?

Risk Score = Probability × Impact

For example:

• Probability 3 × Impact 4 = Score 12 (Medium)
• Probability 5 × Impact 5 = Score 25 (Critical)

What do the severity levels mean?

Severity	Score Range	Meaning
Low	1-4	Minimal concern, monitor as needed
Medium	5-12	Moderate concern, plan mitigation
High	13-16	Significant concern, prioritize attention
Critical	17-25	Urgent concern, immediate action required

Can I customize the severity thresholds?

No. The severity thresholds are fixed based on the standard 5×5 risk matrix methodology. This ensures consistency with industry-standard risk assessment practices.

What’s the difference between Mitigated and Closed status?

• Mitigated: The risk still exists but controls are in place to reduce its likelihood or impact. Continue monitoring.
• Closed: The risk is no longer relevant (threat eliminated, project phase complete, or risk didn’t materialize).

Can I track risk history?

Yes. Every risk has a History tab showing:

• When the risk was created and by whom
• All field updates with old and new values
• Issue linking and unlinking events

Can I delete a risk?

Yes. Open the risk and use the delete action. Deletion is permanent and cannot be undone. Consider exporting risks before deletion if you need a record.

Issue linking

Can I link one risk to multiple Jira issues?

Yes. A single risk can be linked to multiple issues. This is useful when multiple tasks or stories contribute to mitigating a risk.

Can I link the same issue to multiple risks?

Yes. The same issue can be linked to different risks. This is useful when one piece of work addresses multiple risks.

Can I link the same issue to the same risk twice?

No. Duplicate links are prevented. Each issue-risk pair can only be linked once.

Can I link issues from other projects?

No. Issue linking is limited to the current project. This ensures risks and their mitigation work stay within project context.

What information is stored about linked issues?

For each linked issue, the app stores:

• Issue key
• Summary
• Status
• Type
• URL
• Priority (if available)
• Assignee (if assigned)

Bulk operations

Can I edit multiple risks at once?

Yes. In table view, select multiple risks using checkboxes, then use the bulk action bar to:

• Set Probability
• Set Impact
• Set Status
• Set Owner
• Delete selected risks
• Copy as Markdown

What does “Copy as Markdown” do?

This feature copies selected risks to your clipboard as formatted markdown text. Paste it into Confluence, Slack, email, or documentation for easy sharing.

Is there a limit on bulk operations?

There’s no hard limit, but very large bulk operations may take longer to process. For best results, work with reasonable batch sizes (e.g., under 100 risks at a time).

Import and export

Does the app support CSV import and export?

Yes. You can:

• Export All Risks: Download the complete risk register
• Export Filtered Risks: Download only risks matching current filters
• Import CSV: Bulk create risks from a CSV file

What’s the CSV format for import?

Required columns:

• Title (max 200 characters)
• Description (max 1000 characters)
• Status (open, mitigated, or closed)
• Probability (1-5)
• Impact (1-5)
• Mitigation (max 1000 characters)

Tip: Export first and use that file as a template for imports.

Can I import risks with owners?

Yes. Include an “Owner” column with the user’s display name. The name must match exactly a project user’s name.

Can I import risk history?

No. History is not imported. New history starts from the import. The “Created By” will be the user performing the import.

Permissions and access

Who can view and edit risks?

Any user with Browse Projects permission in the project can:

• View all risks
• Create new risks
• Edit any risk
• Delete any risk

Is there role-based access control within the app?

No. The app uses Jira’s project permissions. There are no separate roles within the app.

Can I restrict who can delete risks?

No. Any user who can access the project can delete risks. If you need audit trails, use the History feature to track changes.

Technical

What technology does the app use?

The app is built on:

• Atlassian Forge: Serverless platform for Jira apps
• React: Frontend framework
• Forge Storage: Data persistence (Key-Value Storage)

Does the app work offline?

No. The app requires network connectivity to load and save data.

Does the app have a REST API?

No. The app doesn’t expose a public API. All interaction is through the Jira UI.

Can I use the app on mobile?

The app works in mobile browsers but is optimized for desktop use. Some features may be harder to use on small screens.

Getting help

How do I get support?

• Support portal: https://small-batch.atlassian.net/servicedesk/customer/portal/34
• In-app: Use the footer links for Support

How do I report a bug?

Contact support with:

• Description of the issue
• Steps to reproduce
• Screenshots
• Your Jira site URL and project key
• App version (from footer)