Page Comparison

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.

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:

1. Identify Your Board’s Filter:

   • Begin by locating the filter associated with your board. This filter controls which issues are displayed on the board.

Image Added

2. 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.

3. 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.

Image Added

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."

1. 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.

2. 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.

3. 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.