FAQ

Why are risks not work items?

A risk register has to stand up to an audit, and work items are built for a different job. If risks were work items, the app would need its own work item type, custom fields and changes to the permission scheme, and that needs a Jira administrator. Residual keeps risks as its own records, so the project admin can set it up alone and your Jira schema stays untouched.

Residual also does not put risks on your boards. It is a register for project and programme risks.

Can I link risks to Jira work items?

Yes. A risk can reference Jira issue keys, for example the work item that implements a treatment.

Can I use JQL?

No. Risks are not work items, so JQL does not find them. Use the table and the heatmap on the Risks page, or export the register as CSV for further analysis.

What happens when I uninstall Residual?

The Risks page disappears from your projects. The data of the app is deleted by Atlassian according to the Forge platform standard for uninstalled apps. If you need the register afterwards, export it as PDF and CSV before you uninstall.

Do I need a Jira administrator?

Configuring and using the register only needs Jira project permissions. See Permissions. Installing an app on an Atlassian site follows Atlassian’s standard install process.

Can I change the number of steps in the scales?

No. The model is fixed at five by five. The project admin can adapt the labels and descriptions of the steps and turn on detection as a third dimension. See Risk model.

Is Residual an ISMS or GRC tool?

No. Residual does not map controls to frameworks and does not manage an asset inventory. It is a register for project and programme risks.

Does any data leave my Atlassian cloud?

No. See Data storage and security.