Administrator’s Guide
📌 Overview
Risk Radar is a Jira Cloud app that enables teams to assess execution risks directly within Jira issues. It calculates risk scores based on likelihood, impact, and difficulty, helping teams identify and mitigate potential project risks.
This guide provides installation, configuration, and troubleshooting steps for administrators managing Risk Radar in their Jira instance.
⚙️ Installation & Setup
🔹 Installing Risk Radar in Jira Cloud
Go to the Atlassian Marketplace and search for Risk Radar.
Click Get App and select the Jira Cloud instance where you want to install it.
Confirm installation and grant the necessary permissions.
Once installed, Risk Radar will be available under the Apps section inside Jira issues.
🔧 Configuration & Permissions
🔹 Enabling Risk Radar for Users
By default, Risk Radar is available for all Jira users. However, administrators can restrict access by adjusting Jira global permissions:
Go to Jira Settings → System → Global Permissions.
Under Application Access, configure which user groups can access third-party apps.
🔹 Managing App Licenses
Ensure that the license is active in the Atlassian Marketplace under Manage Subscriptions.
If the license expires, users will no longer be able to use Risk Radar.
🔹 Configuring Risk Assessment Settings
Risk Radar uses predefined risk factors for assessment, but administrators can:
Enable/Disable commenting on issues when risk assessments are saved.
Monitor how risk scores impact issue prioritization in Jira dashboards.
🛠️ How to Use Risk Radar
🔹 Assessing Risks in an Issue
Open any Jira issue and navigate to the Apps panel.
Select Risk Radar to open the risk assessment tool.
Choose:
Likelihood: Low, Medium, High
Impact: Minor, Moderate, Critical
Difficulty to Fix: Easy, Medium, Hard
Risk Radar will generate a risk score (1-10) based on your input.
🔹 Saving Risk Assessments
The calculated risk score is stored in the Issue Properties within Jira.
Optionally, the risk score can be added as a comment in the issue for visibility.
📌 Searching Issues by Risk Score in Jira
This guide provides instructions for Jira administrators on how to search for issues with risk scores using JQL queries. If the "Save as Comment" option was checked in the application, risk scores are stored as comments, allowing admins to filter and track risk levels through JQL.
🔍 Searching for Risk Scores via JQL
Jira administrators can use JQL queries to find issues based on their risk levels. If the application has been configured to save risk scores in comments, admins can retrieve issues using the following JQL queries:
🔹 Search by Risk Category
To find issues based on risk category, use:
comment ~ "Saved Risk Score: Low Risk"
comment ~ "Saved Risk Score: Medium Risk"
comment ~ "Saved Risk Score: High Risk"
🔹 Search by Exact Risk Score Value
If you want to search for a specific numeric risk score, such as 6.9
, use:
comment ~ "Saved Risk Score: 6.9"
✅ Best Practices
Ensure comments are enabled for risk score storage – If the "Save as Comment" option was not selected in the application, these queries will not return results.
Encourage teams to use JQL filters – Help users create and save their own queries to monitor risk.
Automate tracking with Jira Dashboards – Set up automated reporting to ensure timely risk assessment.
By using JQL search, filters, and dashboards, administrators can efficiently track and manage risk levels across Jira projects. 🚀
🚨 Troubleshooting & Support
🔹 Common Issues & Fixes
Issue | Possible Cause | Solution |
---|---|---|
Risk Radar is not appearing in issues | App is not installed correctly | Reinstall from the Atlassian Marketplace |
Risk scores are not saving | API permission issues | Check app permissions in Jira |
License validation failed | Expired license | Renew via Atlassian Marketplace |
Cannot add risk assessment comment | User lacks comment permissions | Grant comment permissions in Jira settings |
🔹 Contacting Support
For further assistance, reach out via:
📩 Email: riskradarjira@gmail.com