Frequently Asked Questions

On this page, we've gathered a comprehensive list of frequently asked questions and common issues to provide you with immediate answers and solutions. This resource is designed to help users navigate the functionalities of Agility Poker Planning app more effectively, offering clear, concise responses to your queries.

Whether you're encountering a technical challenge, seeking guidance on how to use a specific feature, this FAQ section is your go-to guide. We regularly update this section to include new information and insights, ensuring that it remains a relevant and valuable tool for all our users.

How much does the plugin cost? Is it possible to pay only for users who utilize Agility Poker Planning for Jira?

The Agility Poker Planning application is available at no cost, allowing unlimited user access on your Jira instance.

How do I locate and use the Agility Poker Planning for Estimation Tool for Jira plugin?

To use the Agility Poker Planning for Jira, go to the left side menu in any project or board. There, in the app section, you'll find the Agility Poker Planning for Jira tab, which opens its specific dashboard. You can also locate the application in the top right corner of the standard Board view for easy access.

Jira compatibility - project types we support

We currently actively support:

Jira - Software Projects

We do not support - some functionality may still work but we cannot guarantee:

Jira - Business Projects
Jira Service Management
Jira - Product discovery

If you have issues please check your project type first before diagnosing and contacting us.

Why Are No Jira Issues Loading When Creating a Session?

If you're experiencing issues with Jira not loading any issues when creating a session, this could be due to an incorrect board filter configuration. Here’s how to troubleshoot and resolve the problem:

Identify Your Board’s Filter:
- Begin by locating the filter associated with your board. This filter controls which issues are displayed on the board.

Check for Errors:
- If you encounter an error message such as "A value with ID '123' does not exist for the field 'project'," this indicates that the board filter is misconfigured. This issue often arises after migrating a board or issues.
Correct the Filter:
- To resolve the issue, you'll need to correct the project field in the filter. Replace the incorrect project reference with the correct project name or key. You can use the project key acronym found in Jira ticket IDs (e.g., "COM-1" where "COM" is the project key) to identify the correct project.

By updating the filter to correctly reference your project, you should be able to load issues without any problems when creating a session.

In addition to the board filter, another common reason why Jira issues may not load when creating a session is the configuration of the estimation field, such as "Story Points" or "Story Point Estimate."

Visibility of Estimation Field:
- The estimation field (e.g., "Story Points" or "Story Point Estimate") must be visible and properly configured in the context of your Jira project's field configuration. If this field is not set up or is hidden, Jira will be unable to load issues that depend on this field for estimation.
Configuration Check:
- Ensure that the estimation field is added to the relevant issue types and screens within your project. This can be done through Jira's field configuration settings, where you can check that the field is not hidden and is associated with the correct screens and contexts.
Impact of Misconfiguration:
- If the estimation field is not configured correctly, or if it is missing from the project's field configuration, Jira will not be able to load the issues when you try to create a session that relies on this field. This could cause errors or result in an empty list of issues being displayed.

By ensuring that the estimation field is correctly configured and visible, you can avoid potential issues when creating sessions and ensure that all relevant issues are properly loaded.

Why can't I find any users in the dropdown when selecting a moderator, participant, or observer?

Ensure that the appropriate permissions are set for the application and user group. The permissions should allow the group to "Browse users and groups" under the "atlassian-addons-admin" group. Also, verify that the user creating the session is part of the correct user group, which could be under "jira-users-x."

Why am I receiving an error message when trying to save story points?

The issue with saving estimates in Jira might stem from particular configuration settings. It's crucial to verify that the estimation field is appropriately configured and deemed valid for the necessary issue types. If you're unable to view specific issues, such as bugs or tasks, in Agility Poker Planning for Jira, this suggests that an estimation field, like Story Points, needs to be included for these issue types. For comprehensive guidance on how to configure this, please consult the available documentation here Jira Configuration. Adhering to these instructions should enable smooth estimate saving in Jira.

Other error messages relating to this include:

Answer: This error typically occurs when the estimation values being used don't align with Jira's expected format for the Estimation Field. For instance, if you've chosen 'Time Estimations', the data is formatted to suit the 'Original Estimation' field, not the 'Story Point' field. Consequently, Jira rejects this mismatched format, leading to the error. To resolve this, please ensure that your selected estimation value correctly corresponds with the Estimation Field you intend to use. Remember, you can adjust the estimation settings either when initiating a session or while editing within an existing session. By aligning your estimation values with the appropriate field, you should be able to save story points without encountering this error.

Why am I unable to cast votes on issues in the Agility Poker Planning session?

Agility Poker Planning for Jira incorporates various user roles to facilitate efficient teamwork. As part of the setup process, users are assigned specific roles. Generally, only those designated as moderators and estimators are granted the right to vote on issues. Observers, on the other hand, do not have this voting privilege.

If you're experiencing difficulties in voting on issues within Agility Poker Planning for Jira, it's likely that your current role is that of an observer. However, you can switch to a participant role simply by clicking the participant button within the session, which will then enable you to engage fully and cast your votes.

As a moderator, how can I invite users to the Agility Poker Planning session?

In Agility Poker Planning for Estimation Tool for Jira, each session you create generates a distinct link that can be distributed through email or any other preferred method of communication.

To obtain this session link, simply go to the session's page and use the copy link button. Alternatively, the link can be copied directly from the browser’s address bar or by using the copy link feature found in the breadcrumbs of the estimation session.

Sharing this link is advantageous as it eliminates the need to manually add each user as a participant. By clicking on the shared link, users are automatically included as participants in the session. Please note that for private sessions, participants or observers must be pre-added in the session's settings before they can join.

Is it possible to have multiple moderators in a session?

No, a session is limited to just one moderator at any given time.

Why am I receiving an error when using the filter, and how do I use JQL?

To use JQL in the search filter, type queries to find issues that match specific criteria. Here are some common examples:

Search by Issue ID: id=COM-01
Find Issues with No Story Points: 'Story Points' IS EMPTY
Filter by Issue Type (e.g., Story or Task): IssueType="Story"
Filter by Labels: labels=X

You can also combine conditions, like 'Story Points' IS EMPTY AND labels=X, to refine your search.

For more details, check the JQL wiki page.