Support
Riskcadence for Jira
Get help
Have a question, found a bug, or want to request a feature? We're happy to help. Email us in English or German and we typically respond within 1–2 business days, or open a public issue on GitHub. Check the existing issues first: your question may already have an answer.
Email: support@janekbehrens.de
Bug reports & feature requests: github.com/janekbehrens/riskcadence-issues
Documentation: Riskcadence for Jira documentation
Response time: 1–2 business days (Monday to Friday)
Before you reach out
Most questions are answered in the documentation. Common ones:
- How do I set up a team-managed project? Jira does not let apps add work types or fields there, so a project admin adds the work type Risk and seven fields once, with the exact names Riskcadence lists, and then clicks Finish setup (setup).
- Risk score and Risk level are missing on the work item: in team-managed projects Jira does not show app-calculated fields. Riskcadence still shows score and level in the register, the panel and the reports (fields).
- The register shows only 2,000 risks: in a bigger register the filters run in Jira and reach every risk, and the list shows the 2,000 most recently updated matches. Narrow the view with a filter (limits).
- How do I link mitigations? Link a work item to the risk with the link type is mitigated by. The risk then shows how many of its mitigations are done (panel).
- "Former user" in a report: the risk owner's Atlassian account was closed, and Riskcadence erased it from what it stores (details).
- "A review of this project is already open": a project has one open review at a time. Open it and close it before you start a new one (reviews).
- "The Riskcadence license on this site is not active": the trial or subscription has ended. Ask a Jira admin to start or renew it.
What to include in a bug report
- Where it happens: the register, the matrix, the issue panel, a review, the report, the Confluence macro, a dashboard widget or the import
- What you did and what Riskcadence shows: the title of the message, or a screenshot (it helps a lot)
- Company-managed or team-managed Jira project, and your role (Jira admin, project admin or member)
- For an import: the number of rows and the message of the failed row (please do not send risk contents)
Legal: Privacy Policy · Terms of Service · Security Policy