Child pages
  • Configuring estimation field for Company-managed projects

Our new Appfire Documentation Space is now live!

Take a look here! If you have any questions please email

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »


Error rendering macro 'excerpt-include'

User 'null' does not have permission to view the page.

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 estimate only issues that estimation field is set as valid for the right issue types. If some issues (e.g. bugs, tasks) are not visible in Agile Poker for Jira it means you have to add estimation field (for example: Story Points) to relevant issue type.

How can I add Story Points to a custom issue type?

To enable the Story Points for different issue types first go to the Project Settings -> Fields -> Actions/Edit Fields -> Custom Fields

Find Story Points on the list and then click on the three dots icon and select Contexts and default value.

That should let you change the context of the field to include other issue types. Click on Edit Configuration

And then please select the applicable issue types.

You may also need to add Story Points field to relevant screens sometimes the Field Configurations may also be hiding the Story Points.

Configuring estimation field

For scrum boards the field can be defined in board configuration. For kanban boards you can define the estimation field in the poker session settings.

Managing fields visibility in Jira is a tricky topic and we recommend using field helper for this:

  1. Open the issue you want to estimate in a new tab.
  2. Click Admin -> Where is my field as shown on the screenshot below:
  3. Type the field name and you will see why the field is not visible.

If you want to know more about field visibility take a look at the following articles in Jira documentation:

  1. Configuring a screen's tabs and fields.
  2. Associating a screen with an issue operation. 


  • No labels

This page has no comments.