Troubleshooting Planning Poker Agility

No issues load when I create a session

• Check the board’s filter. Sessions load issues through the board. If the board’s filter shows an error such as “A value with ID '123' does not exist for the field 'project'”, often after a board or its issues were moved, edit the filter and replace the wrong project with the right project name or key (the letters before the number in an issue key, such as COM in COM-1).
• Check the estimation field. It must be available for your issue types and visible on their screens. See Set up the estimation field.
• Check estimation is on. In a team-managed project, turn on Estimation under Project settings, Features.
• Done issues are not listed, and sub-tasks show only with Enable Subtasks on.

Set up the estimation field

The agreed estimate is saved to the field you pick as the session’s Estimation field. Jira accepts it only if that field is available for the issue’s type and on the issue’s screen. Otherwise saving shows Error while saving estimate, for example “Time tracking field must be present on the corresponding Screen for any estimation value to be saved” for Original estimate. These steps need a Jira admin.

Company-managed projects

1. Make the field available for your issue typesIn Jira’s settings, go to Issues, Custom fields. Find Story Points, open its menu (•••) and choose Contexts and default value. Edit the context so it includes every issue type you estimate, such as Bug and Task, and save.
2. Put the field on the screenIn Jira’s settings, go to Issues, Screens. Find the screen your project’s issue types use, open its menu (•••) and choose Configure. Add Story Points, or Time tracking if you save to Original estimate: Original estimate is part of Time tracking.
3. Check the field is not hiddenIf it still doesn’t show, open an affected issue, open its menu (•••) and choose Find your field. Jira says why a field is hidden, for example by a field configuration.

Team-managed projects

• Go to Project settings, Features and turn on Estimation. This adds Story point estimate to the project’s standard issue types.
• To save to Original estimate, the issue type’s fields must include Time tracking (Project settings, Issue types).
• Number fields you create in the project work too, once they are among the issue type’s fields.

Kanban boards

Kanban boards have no estimation field of their own. Pick a number field, such as Story Points, as the session’s Estimation field, and make sure it is on the screens of the board’s issues as above.

Match the cards to the field

Time values such as 1d or 30m can only be saved to a time field such as Original estimate. Numbers suit Story Points and other number fields. If Jira refuses the value, change the cards or the field from the session’s settings (cog).

Filter issues with JQL

When you select issues, the Filter box takes an issue’s name or a JQL query. A valid query narrows the list to the issues that match. Some examples:

• One issue: key = COM-1
• Issues with no story points: "Story Points" IS EMPTY
• One issue type, such as stories: IssueType = Story
• A label: labels = X
• Combine conditions with AND: "Story Points" IS EMPTY AND labels = X

If you see Invalid JQL query: please check the field type and format, then try again., check the field names and quotes: a field name with spaces needs quotes, and the field must exist on your site. Your query only narrows the list: issues in a Done status never show, and sub-tasks show only with Enable Subtasks on.

Error: “The value 'Sub-task' does not exist for the field 'issuetype'”

In company-managed projects, Planning Poker Agility looks for sub-tasks by Jira’s standard Sub-task issue type. If that type was removed, renamed or replaced by a custom sub-task type, loading issues fails with this error. A Jira admin can fix it by restoring the standard Sub-task issue type. Custom sub-task types are not supported.

No users in the dropdown

The Moderator, Participants and Observers pickers search your Jira site’s users with your own account. The app also looks people up with its own app account, which belongs to the atlassian-addons-admin group. If the pickers find nobody, or names and avatars are missing, a Jira admin should give the global permission Browse users and groups (in Jira’s settings, System, Global permissions) to atlassian-addons-admin and to the groups your team belongs to, and check you belong to one of those groups.

I can’t vote

If the session says You are currently an observer, choose Participate. You can’t vote until the moderator chooses Start estimations for the issue.

I can’t join a session

A private session opens only for the person who created it, its moderator and the people added to it, so Join session is greyed out for everyone else. Ask the moderator to add you. A finished session can be viewed but not joined.

Still stuck?

Contact support and tell us what you see, or use Need Assistance? on the All sessions page.