In the released Source → Design plugin, I ran into a PostgreSQL availability issue: the application returned an error connecting to the server. The risk was that a user would be unable to finish what they were doing in the plugin. Even a temporary failure could damage trust, especially if this was someone’s first experience with the product.
The error made it clear that I needed to consider database availability separately from whether the application itself was working. I assessed the impact by considering which actions would become unavailable and whether a user could retry the operation without losing their work.
The experience showed me that a risk assessment needs to be updated when real evidence emerges, even if the problem initially seemed unlikely.
I develop Risk Radar for Jira at TypeSwitch. It lets Jira Cloud teams select likelihood, project impact and difficulty to fix, then save the assessment on an issue.
https://marketplace.atlassian.com/apps/1237030/risk-radar-for-jira-risk-management-assess-track
