I'm looking to use JIRA to track risk and issues in a standard project management environment (i.e. the project isn't specifically agile development orientated). We like the collaboration features but don't need to relate our risks and issues to development tasks.
I realise we could create a category of issue named 'risk' and add the fields we want and appropriate workflow but thought someone must have done this before. Does anyone have a configuration of risks/ issue fields etc. which would be suitable?
SoftComply has developed a risk management add-on for JIRA Cloud users that is fully customizable - https://marketplace.atlassian.com/plugins/com-softcomply-riskmanager-cloud/cloud/overview
For more information, please do not hesitate to contact us at firstname.lastname@example.org / www.softcomply.com
I had one customer who had Risk as an issue type. Pretty straight forward config.
Had summary, description, severity and owner as fields. Workflow was just Open and Closed. They were linking the risks to other issue types and was using the links in workflow conditions.
I know this is an old thread, but I can't resist. I've just built a plugin for JIRA that does the configuration for you. See http://www.projectbalm.com/risk-register/. It can be very tricky doing the kind of configuration you are imagining, especially when schemes are shared between projects. The Risk Register plugin creates a new Risk issue type, and sets you up with the field schemes, screen schemes, issue type schemes that you need. It also creates a workflow that is automatically attached to Risk issues. You can view your risks in a colorful risk matrix too.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG