JIRA RiskManagement

Added by Jes A, last edited by Jes A on Oct 28, 2008  (view change)
Name RiskManagement
Author(s) Jes A
License Commercial License and Trial terms
Price 299$ BUY NOW (Redirect to PayPal)
IssueTracking http://developer.atlassian.com/jira/browse/RSK
Download See Version History at this page
Jira version See Version History.
A user has reported that the plugin only works with the Jira Enterprise edition, but this is not verified

Trial & Purchase

You can try the plugin out for free for one month.

Buy Now (Redirect to PayPal)

License and Trial terms

Price

Price including 12 months maintenance: 299$

Renewal of maintenance (12 months): 149$

Description/Features

RiskManagement report and portlet provides risk management functionality.

Risk Management Concepts

Most project management models operate with risk management as an important part of achieving successful projects.

Since Jira is an excellent tool for registering all project issues, why not also registry the project risks!

The RiskManagement report and portlet makes it possible to track risks dynamically and present them graphical for decision makers etc.

The generally idea in the RiskManagement plugin is to multiply the probability and the consequence for a given risk. The product of the probability value and the consequence value (the Risk Number) decides how critical the risk is.

In the RiskManagement plugin you can mark an issue (a potential risk) with a probability and a consequence value from 0-5. That is the Risk Number will be from 0-25. The RiskManagement plugin places the risk issues in a matrix like the one below.   










Report and Portlet

The RiskManagement plugin comes with a report, two portlets and a project tab.

You can choose to use either a filter or a project to filter out issues. All issues with a Risk Number lower than 1 will be ignored.

You can also choose to run the report or portlet with a past date, given you the possibility to see the status of the risk as there were a week or a month ago. The date can either be relative (e.g. 3 months ago) or exact. 

CustomFields

RiskManagementCalculatedCustomField-- a mandatory custom field you will have to add. It calculates the Risk Number - the product of the probability and the consequence.

Furthermore, you will have to add custom fields for registering the probability and consequence values.

Usage and Installation

Note: If upgrading, please note that the installation and configuration is quite different from version 1.x.

  1. Install the plugin by
    1. Unzip the zip file.
    2. Copy the JAR to WEB-INF/lib inside your JIRA web application.
    3. Copy the folder "com" to WEB-INF/classes .
    4. Note: If upgrading from a previous version you must delete or over write the existing jar, folders and misc files.
  2. Go to Administration > Custom Fields and add two custom fields for the Probability and Consequence values.
    • Recommendation: Make the fields of the type Select List. Add to each of the fields values 0,1,2,3,4 and 5. Make 0 the default value.
    • Recommendation: Name the fields "RiskProbability" and "RiskConsequence".
  3. Go to Administration > Custom Fields and hoover the curser over the "configure" label of the fields you just created. The URL in your browsers status line will show the customFieldId. Write the ids down.
  4. Create two new filters and save them. Set Column Order for the filters. The Column Order of these filters decides the default layout of the report and project tab.
    • Atlassian documentation for: How to save a filter
    • Tip: You can use the same filter for both the report and the project tab.
  5. Go to Manage filter. Find the filters you just created and hoover the curser over the links in the same row as the filter. The URL in your browsers status line will show the filter's id. Write the id down.
  6. Open the file WEB-INF\classes\com\ja\jira\plugin\report\riskmanagement\riskmanagement.properties in a texteditor.
    1. Replace the fields id with the new ones.
      • riskmanagement.field.mandatory.probability
      • riskmanagement.field.mandatory.consequence
    2. Replace the filters id with the new ones.
      • riskmanagement.columnlayout.report.id
      • riskmanagement.columnlayout.projecttab.id
    3. Specify the user who has privileges to use the filter (normally the same user who created the saved filter).
      • riskmanagement.columnlayout.user
    4. Allow or disallow a user to use individual filters to decide the report layout (true or false).
      • riskmanagement.columnlayout.userenabled
  7. Restart JIRA
  8. Go to Administration > Custom Fields and add a new custom field of the type RiskManagementCalculatedCustomField.
    • Note: You must set the field type to RiskManagementCalculatedCustomField.
    • Recommendation: Name the custom field "RiskNumber".
    • Note: You will probably need to reindex Jira before you can search for issues with a certain risknumber
  9. Now you can add the RiskManagement portlet to your Dashboard, view the RiskManagement report from any projects Browse Project page or a Project Tab.
    • You probably want to Set Column Order for your saved filters again to include "RiskNumber".

Customization

Labels (Language)
Editing the labels should be straight forward.

Custom fields and standard issue fields
You can easily add new fields to the report. Just set Column Order for the filter. See the installation guide.

Report design, colors, fonts etc.
By editing the velocity files you can change the view of the report, portlet and project tab.

Allow or disallow whether or not a user can use individual saved filters to define the layout of the report. 
Set the property riskmanagement.columnlayout.userenabled to true or false.
Example: riskmanagement.columnlayout.userenabled:false 
Define the number of cells in the matrix.
riskmanagement.matrix.number_of_cells:5
In this example the matrix will be 5x5 cells. Setting the value to 4 will change the matrix to 4x4 cells. One would probably also want to set the boundaries for red and yellow risks and some of the HTML in the velocityfiles.

Lower boundaries for yellow and red issues
riskmanagement.matrix.yellow_lower_boundary:5
riskmanagement.matrix.red_lower_boundary:12
Changing for example the value for red risks to 15 will cause that a red risk must have a risknumber equal or greater than 15. 

Version History

Plugin Version JIRA Version Date Comments Binary Souce
2.5 3.13.x 2008.10.28 Updated to work with Jira 3.13.
Notice new license terms (commercial license) 		riskmanagement_bin_v2.5.zip n/a
           
2.41 3.12.x 2008.08.06 One can set up that resolved issues will be filtered out. riskmanagement_bin_v2.41.zip riskmanagement_source_v2.41.zip
2.4 3.12.x
2008.05.24
Added a new portlet which will show the sum of red, yellow and green issues for each relevant project.
riskmanagement_bin_v2.4.zip riskmanagement_source_v2.4.zip
2.32 3.12.x
2008.05.12
Compiled against 3.12.3. Fixes a few none reported bugs.
riskmanagement_bin_v2.32.zip riskmanagement_source_v2.32.zip
2.31 3.10.x
2007.12.16
Now also with German labels.
riskmanagement_bin_v2.31.zip riskmanagement_source_v2.31.zip
2.30 3.10
2007.09.01
Compiled against Jira 3.10.2.
Introduces a number-range searcher, so that one can search for issues that have a RiskNumber within a certain range. 		riskmanagement_bin_v2.30.zip riskmanagement_source_v2.30.zip
2.25 3.7 & 3.8
2007.03.27
Fixes this bug / change request RSK-6
riskmanagement_bin_v2.25.zip riskmanagement_source_v2.25.zip
2.24 3.7 2007.03.19 Fixes this bug RSK-5 riskmanagement_bin_v2.24.zip riskmanagement_source_v2.24.zip
2.23 3.7
2007.03.08
Fixes this bug RSK-3
riskmanagement_bin_v2.23.zip riskmanagement_source_v2.23.zip
2.22 3.7 2007.01.10
  • Enabled the possibility to define boundaries for when an issue is red, yellow or green.
  • Added a link for the matching report in the portlet.
 riskmanagement_bin_v2.22.zip riskmanagement_source_2.22.zip
2.21 3.7 2007.01.08 Bugfix riskmanagement_bin_v2.21.zip riskmanagement_source_2.21.zip
2.20 3.7 2007.01.01 Updated to work with Jira 3.7
  • Bugfix: Relvative date wasn't 2007 compatible.
 riskmanagement_bin_v2.20.zip riskmanagement_source_2.20.zip
2.10 3.6.x
n/a New features:
  • Possible to allow (or disallow) a user to use individual filters to define report layout
  • Misc bugfix's
 riskmanagement_bin_v2.10.zip riskmanagement_source_2.10.zip
2.00 3.6.x n/a New features:
  • More flexible customization of the report - The report uses a Saved Filter to set Column Order.
  • Added a project tab
  • Added localization, English and Danish.
  • Misc bugfix's
    
1.04 3.6.x n/a Bugfix.    
1.03 3.6.x n/a Bugfix, risk date was cached    
1.02 3.6.x n/a 2006.08.04 Added user specific title for portlet.    
1.01 3.6.x
n/a Added relative risk date select.    
1.0 3.6.x n/a First checkin - Report and portlet. Only tested on v. 3.6.1    

Open Issues

Screenshots

Screenshots
The report
Configure portlet
Configure report. User is disallowed to use personal filters to define report layout.
Configure report. User is allowed to use personal filters to define report layout.
Project Tab
The portlet v. 2.22

Labels

jira jira Delete
plugin plugin Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.

Comments (99)

 

  1. Aug 02, 2006

    didier says:

    Very interesting approach but  here are a few things you could add as the...

    Very interesting approach but  here are a few things you could add as

    • the time to mitigate the risk,
    • the cost of the consequence if the risk happen,
    • the cost of the action to launch in order to mitigate the risk,
    • who will run the action.

    Our 2 cents on how this can be improved but this is definitely a very good idea. 

  2. Aug 02, 2006

    Jes A says:

    Actually I think your request already is implemented. Your can just add your ow...

    Actually I think your request already is implemented.
    Your can just add your own custom fields where you can put whatever info your want.
    /Jes

  3. Aug 07, 2006

    Jonathan Nolen says:

    Wow – that's really pretty cool. Totally simple and it just works: very im...

    Wow – that's really pretty cool. Totally simple and it just works: very impressive.

  4. Aug 30, 2006

    David Jarmoluk says:

    Very nice. Any suggestions on how to also get a report view of the issues that a...

    Very nice. Any suggestions on how to also get a report view of the issues that appear on the graph? I thought I'd create a filter, but RiskNumber is not a field you can use when setting a filter.

    1. Aug 31, 2006

      Jes A says:

      Hi David, Have you added the RiskCalculatedCustomField? If you have you can mak...

      Hi David,

      Have you added the RiskCalculatedCustomField? If you have you can make it apear in a filter list.

      Futhermore you will have to edit the .properties file and add the fields (customfileds or Issue fields) you want to be displayed by the report.
      So yes, a report view containing the RiskNumber is possible (In fact you can run neither the portlet nor the report without this field)
      /Jes

      1. Nov 14, 2007

        Tom Miller says:

        What would you suggest as the RiskCalculatedCustomField type? Would a read ...

        What would you suggest as the RiskCalculatedCustomField type? Would a read only text field be appropriate?  When you mean mandatory in the instruction you mean the field must be there for the system to work or the field should be marked as a required field.  Sorry about the dumb questions.

        1. Nov 20, 2007

          Jes A says:

          Ups - didn't notice this comment. RiskCalculatedCustomField is the field that wi...

          Ups - didn't notice this comment. RiskCalculatedCustomField is the field that will calculate and show the risknumber - so yes, it must be there for the plugin to work. Cheers, Jes

  5. Aug 31, 2006

    David Jarmoluk says:

    Sorry. I meant as a dashboard plugin. I thought I would use a filter viewer, but...

    Sorry. I meant as a dashboard plugin. I thought I would use a filter viewer, but you can't filter by the RiskNumber field.

    1. Sep 01, 2006

      Jes A says:

      Hi David, There is a Dashboard portlet available - you just have to add to your...

      Hi David,

      There is a Dashboard portlet available - you just have to add to your dashboard. A filter view, containing the selected fields of a saved filter, is currently not (as far as I know)  a standard JIRA feature.
      The JIRA TimeTracking Reporting Collection contains such a portlet that can do that. I think I will soon separate that portlet from the TimeTracking pluging.

  6. Sep 07, 2006

    Simon Taylor says:

    I like this a lot. I want to display one per project on the project summary page...

    I like this a lot. I want to display one per project on the project summary page in similar fashion to the way the Calendar Plugin adds an html calendar to another tab. Have you considered extending it to do so?

    Simon 

    1. Sep 08, 2006

      Jes A says:

      Simon - no, but it's a good idea. Will look into it, but can't say when. Should...

      Simon - no, but it's a good idea. Will look into it, but can't say when.

      Should it display only the matrix or also the list of "risk" issues ?
      /Jes

      1. Sep 08, 2006

        Simon Taylor says:

        Both i think - the only thing you want to know is how many issues at risk and wh...

        Both i think - the only thing you want to know is how many issues at risk and what they are - and if you dont have to drill to get it all the better.

        The next thing you want to do is to quantify the consequence - i guess this could live in the comments - be good to have another field for it - guess the plugin doesnt need to provide that though - any old custom field could do. 

        1. Sep 11, 2006

          Jes A says:

          Hi Simon, I have deliberately not added any other custom fields than RiskNumber...

          Hi Simon,

          I have deliberately not added any other custom fields than RiskNumber, RiskProbability and RiskConsequence, because it's likely that we all have different requirements.

          But hopefully you are aware that you easily can add custom fields (for example a field where the consequence is quantified) to the report. You can do that by editing the .properties file.

          /Jes

    2. Sep 21, 2006

      Jes A says:

      Simon, see version 2.00. Added a Project Tab. /Jes

      Simon, see version 2.00. Added a Project Tab.

      /Jes

    3. Jan 08, 2007

      Andrew Pidcock says:

      We'd also really like a corporate-wide RADAR like Simon, where you could view th...

      We'd also really like a corporate-wide RADAR like Simon, where you could view the highest risks over all projects for the company in one view.

      1. Jan 08, 2007

        Jes A says:

        "Corporate-wide RADAR". Could you elaborate on this a bite - I'm not sure that I...

        "Corporate-wide RADAR". Could you elaborate on this a bite - I'm not sure that I the purpose of you request.
        Can you use a filter to filter out the highest risks?

        1. Jan 12, 2007

          Andrew Pidcock says:

          A way to view all the risks across all projects

          A way to view all the risks across all projects

          1. Jan 12, 2007

            Andrew Pidcock says:

            Am I right in thinking we could modify this to display the first few words of th...

            Am I right in thinking we could modify this to display the first few words of the task easily, by altering the XML?

            1. Jan 12, 2007

              Jes A says:

              I think the best solution would be one of two options: 1) Develop a new customf...

              I think the best solution would be one of two options:

              1) Develop a new customfield as an plugin to display exactly one you want.

              2) Modify the velocity file:

              Lets say you only want to display the first 10 characters of the summary in the report. In the riskmanagementreport.wm file locate this code at around line 190.
              Here one could add an elseif conditional identifying the summary field, and then just use a substring to reduce the length of the returned string

              #if($matrix.isRiskNumberField($item))
#rowstyle($matrix.getRiskNumber($issue))

#elseif($item.getNavigableField().getName().equals("Summary") && $issue.getSummary().length() > 10)
 $issue.getSummary().substring(0,10)

#else
$item.getHtml($emptyMap,$issue)
#end

              Remember to add some css formatting.

              Haven't tested it, but can't see why it shouldn't work. It will only work for system fields. But one could do pretty much the same with customfields.

              Cheers

      2. Jan 12, 2007

        Jes A says:

        A saved filter with risks from all projects should do the trick.

        A saved filter with risks from all projects should do the trick.

  7. Oct 12, 2006

    Dan Albarran says:

    Is it possible to change what cells are considered high, medium and low risks? W...

    Is it possible to change what cells are considered high, medium and low risks? We use slightly different cells for green, yellow and red.

    1. Oct 14, 2006

      Jes A says:

      Depends on your requirements. For the moment you will have to edit the velocity ...

      Depends on your requirements. For the moment you will have to edit the velocity files and/or the source - it can not be done through the .properties file.

      But will soon upload a new version and can easily make the configuration of the size of the matrix and the definition of what is low (green), medium (yellow) end high (red) risks available in the .properties file.

  8. Dec 31, 2006

    Ronald de Vries says:

    I tried to add this to a Jira 3.7-184 and it crashes the server. How can I best ...

    I tried to add this to a Jira 3.7-184 and it crashes the server. How can I best report/interact on a fix?

    1. Jan 01, 2007

      Jes A says:

      Ronald - Uploaded a new version. Should work with version 3.7.

      Ronald - Uploaded a new version. Should work with version 3.7.

  9. Jan 01, 2007

    Ronald de Vries says:

    Jes, it works indeed with Jira 3.7-184EE, thanks for the quick response.

    Jes, it works indeed with Jira 3.7-184EE, thanks for the quick response.

  10. Jan 09, 2007

    Dan Albarran says:

    I changed the lower boundaries in the properties files to riskmanagement.matrix....

    I changed the lower boundaries in the properties files to riskmanagement.matrix.yellow_lower_boundary:5
    riskmanagement.matrix.red_lower_boundary:12

    However, it does not appear to work. The boundaries are still the same as in your screen prints. Am I doing something wrong?

    1. Jan 09, 2007

      Dan Albarran says:

      Sorry I should have said riskmanagement.matrix.yellow_lower_boundary:8 riskman...

      Sorry I should have said

      riskmanagement.matrix.yellow_lower_boundary:8

      riskmanagement.matrix.red_lower_boundary:15

    2. Jan 09, 2007

      Jes A says:

      Hi Dan, Should work in version 2.22. It wasn't probably enabled in the velocit...

      Hi Dan,

      Should work in version 2.22.

      It wasn't probably enabled in the velocity files which generates the html.

      1. Jan 16, 2007

        Dan Albarran says:

        Thanks! It works. This is now in production and being used by our project ma...

        Thanks! It works. This is now in production and being used by our project managers

        Great Job!

  11. Jan 18, 2007

    Stephen says:

    I am unable to get the portlet to work correctly.  However, the project tab...

    I am unable to get the portlet to work correctly.  However, the project tabs and reports to do work.  Where can I create a Problem Report with the outputed error?

    1. Jan 20, 2007

      Jes A says:

      Hi, Jonathan has created a Jira project for issue tracking, located at http://de...

      Hi,
      Jonathan has created a Jira project for issue tracking, located at http://developer.atlassian.com/jira/browse/RSK