| Info | ||||||||
|---|---|---|---|---|---|---|---|---|
| Panel | ||||||||
| ||||||||
This page is about Agile Poker for Jira Cloud. Using Data Center? Click here. |
After all team members agree on an issue estimate , you usually want to have the agreed value saved in some Jira custom field (we call it the estimation field).
In Agile Poker for Jira Cloud, you can only estimate issues if the estimation field is correctly configured and valid for the appropriate issue types. If certain issues, such as bugs or tasks, are not visible in Agile Poker for Jira, it indicates that you need to add the estimation field (e.g., Story Points) to the relevant issue type.
In Team-managed projects, you can save estimates to available time fields or to any numeric field, including the Story point estimate field.
On this page:
|
|---|
...
|
|---|
Configuring the Story point estimate numeric field
The For users of Team-managed projects in Jira, it is recommended to utilize the default "Story point estimate" field is recommended in order for you to see your for viewing estimates on the board. This field, unlike other Unlike other numeric custom fields specific to Team-managed projects' numeric custom fields, this field is shared between across all the Team-managed projects . 
and offers the advantage of standardization throughout the organization.
...
To configure the Story point estimate field for the board and Agile Poker to use the default field follow these two simple steps:
...
estimates, follow the steps below:
Open your project, and from the sidebar, click Project settings > Features.
Turn on the toggle for Estimation and ensure that Story Points is selected.
By default, this action will enable the Story point estimate
...
field in the Context fields settings
...
for all standard issue types (Project settings > Issue types > Issue type > Context fields). However, you can customize this configuration to suit your needs, so make sure the Story point estimate field is enabled in the Context fields.
When creating a session in Agile Poker, select the Story point estimate field as the estimation field in the session setup (Agile Poker > Create session > third step for all sessions) or configuration (Agile Poker > Join Session > Configure > Session settings > Estimation field).
If you prefer to use a different field to save your estimates, you can add a number field to the issue type via via Project settings → settings > Issue Types types and set that field as the "Estimation field" like in step 2 aboveestimation field following the same steps as mentioned above in step three.
Configuring
...
numeric custom fields
Any numeric custom field created specifically for a Team-managed project can be estimated using Agile Poker. The only requirement is that the field is present in the Context fields settings (Project settings > Issue types > Issue type > Context fields).
...
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
Numeric custom fields for Team-managed projects are unique and can't be used for other projects. |
Configuring the Original estimate time field
Configuring the Original estimate time field for Agile Poker can be a bit tricky, as it requires Time tracking to be included in the Context fields list. Although you might see the Original estimate field in your issue details and can edit and save it, it may not be available for Agile Poker if Time tracking is missing from the Context fields list.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
To ensure the Original estimate field works properly with Agile Poker, please make sure that both Original estimate and Time tracking are included in the Context fields list for the issue types you plan to estimate. |
...
By default, when you enable the Estimation feature in Project Settings (Project settings > Features > Estimation), the required fields are added to the Context fields list for standard issue types.