Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The RICE model is a product management framework for scoring and prioritizing features. RICE stands for reach, impact, confidence, and effort. You calculate a feature's RICE score by rating it on reach, impact, effort, and confidence in your ratings.

Info

RICE field is only available as a custom field type. It is not possible to define general values or any other settings options in the app configuration screenR(ICE) is not available in Jira Service Management (JSM). For a list of fields that are supported in JSM, please visit Fields in Jira Service Management (JSM) Portal.

...

Note

To create and configure the RICE field custom field, you must be logged in as a user with Jira Administratoradministrator permissions.

...

  1. Go to AppsManage your appsFields

  2. Click on Create custom field button on the right side of the screen.

  3. Select RICE R(ICE) field and click Next.

  4. Name and add a description to your field then click Next.

  5. Choose between using your own inputs or map existing custom fields select mapping existing custom fields where the R(ICE) formula will be applied for value calculation.

Panel
bgColor#DEEBFF
Screenshot 2024-09-29 at 10.58.47.pngImage Added
  • Reach: How many people will the initiative impact?

  • Impact: What is the level of impact on each person? (scored on a 0.25–3 scale).

  • Confidence: How confident are you in your estimates? (0%–100%).

  • Effort: How much time will it take to complete the initiative? (e.g., in person-months).

Screenshot 2024-09-29 at 10.59.51.pngImage Added
  • Impact: What’s the potential impact of the initiative? (scored on a 1–10 scale).

  • Confidence: How confident are you in your estimates? (0%–100%).

  • Ease: How easy will it be to implement? (scored on a 1–10 scale).

  1. Associate the field to the appropriate screens and click Create. You must associate a field to a screen before it will be displayed.

  2. To restrict editing access for the Multilevel Select Picker, the Edit Permissions tab is used. Specific users, user groups, and Jira roles can be defined to have editing permissions for the custom field. If editing access is intended for all users, the field should be left empty.

Info

Please note that the create screen has a separate toggle that allows defining whether users without edit permissions can create values in create screens.