apache/kafka · error · Exception

Didn't find any issues for version {}

Error message

Didn't find any issues for version {}

What it means

release/notes.py:generate queries Jira for `project=KAFKA and fixVersion=<version>` and requires at least one matching issue. An empty result means the version string does not match any fixVersion on any KAFKA issue, so release notes cannot be produced. It raises a generic Exception with the version interpolated (the message in the catalogue is the pre-format template).

Source

Thrown at release/notes.py:148

def issue_str(issue):
    """
    Provides a human readable string representation for the given issue.
    """
    key = "%15s" % issue.key
    resolution = "%15s" % issue.fields.resolution
    link = issue_link(issue)
    return f"{key} {resolution} {link}"

def generate(version):
    """
    Generates the release notes in HTML format for given version.
    Raises an error if there are unresolved issues or no issues
    at all for the specified version.
    """
    issues = query(f"project=KAFKA and fixVersion={version}")
    if not issues:
        raise Exception(f"Didn't find any issues for version {version}")
    unresolved_issues = filter_unresolved(issues)
    if unresolved_issues:
        issue_list = "\n".join([issue_str(issue) for issue in unresolved_issues])
        raise Exception(f"""
Release {version} is not complete since there are unresolved or improperly
resolved issues tagged {version} as the fix version:

{issue_list}

Note that for some resolutions, you should simply remove the fix version
as they have not been truly fixed in this release.
        """)
    return render(version, issues)


if __name__ == "__main__":
    if len(sys.argv) != 2:
        print("Usage: python notes.py <version>", file=sys.stderr)

View on GitHub (pinned to 996fb4585a)

Solutions

1. Confirm the exact fixVersion string in Jira (browse a tagged issue's fixVersion field) and pass that string.
2. Make sure at least one issue has been tagged with this fixVersion before running the script.
3. If the version is genuinely new, tag the relevant issues first, then re-run.
4. Check the Jira connection/credentials used by release/notes.py - an auth failure can also return an empty result.

Example fix

# before
$ python3 release/notes.py 3.7.0.0
Exception: Didn't find any issues for version 3.7.0.0

# after
# verify in Jira that fixVersion is "3.7.0" (not 3.7.0.0)
$ python3 release/notes.py 3.7.0

issues = query(f"project=KAFKA and fixVersion={version}")
if not issues:
    raise SystemExit(f"No Jira issues for fixVersion '{version}'. Verify the name in Jira.")
generate(version)

null

try:
    notes.generate(version)
except Exception as e:
    print(f"{e}; confirm fixVersion '{version}' exists in Jira", file=sys.stderr)
    raise

When it happens

Trigger: Calling generate(version) where `version` is not set as a fixVersion on any KAFKA Jira issue - because the version name is wrong, the release has not been planned in Jira yet, or issues were tagged with a different fixVersion string.

Common situations: Typos in the version argument (3.7.0 vs 3.7.0.0); running notes generation before release issues are tagged; the version exists in Jira under a different naming convention (e.g. with a leading 'Kafka ').

Related errors

• Didn't find any issues for version {version}
• Unexpected contents in the artifact. Exactly one version dir
• GITHUB_TOKEN is not set in the environment
• Failure in executing following command:-
• This field cannot be empty

AI-assisted analysis of apache/kafka@996fb4585a (2026-08-11). Data as JSON: /api/errors/78b3163f47214d51. Report an issue: GitHub.