Setting up the Estimation Field for Kanban Boards

Kanban boards on Jira Cloud do not inherently support estimation functions. To incorporate estimation capabilities using Agility Poker Planning for Jira Cloud on these boards, specific settings need adjustment. These adjustments include:

  • Establishing an estimation field

  • Incorporating the estimation field into the Edit issue interface

This guide is tailored for Company-Managed (previously known as Classic) projects. For those using Team-Managed projects, please refer to the relevant documentation.

Step 1: Establish the Estimation Field When a team reaches a consensus on an issue's estimate, it's essential to have a specific field to record this agreed value. While Scrum boards typically use the Story points field, Kanban boards lack this as a default feature, necessitating the establishment of an estimation field.

To set up the estimation field, do the following:

  1. Access the third step in the session creation process.

  2. Choose an appropriate field from the Estimation field dropdown, either by selecting an existing field or creating a new custom one (refer to Jira's documentation for guidance). If your custom field isn't in the dropdown, ensure that:

    • It is a numeric field, as other types aren't compatible.

    • It appears on the View issue interface for all board issues.

Step 2: Integrate the Estimation Field into the “Edit Issue” Interface If you receive an error when saving an issue estimation, verify that the estimation field is visible on the Edit issue screen.

Managing field visibility in Jira can be intricate. For assistance, use the Field Helper tool by:

  1. Opening the issue in question.

  2. Clicking the three-dot icon, then selecting Find your field on the Edit issue screen.

  3. Entering the field name to receive insights on its visibility.

For more comprehensive understanding of field visibility, consider these Jira documentation topics:

For additional information on field visibility, consider exploring these articles in Jira's documentation