apache/kafka · error · Exception

Didn't find any issues for version {version}

Error message

Didn't find any issues for version {version}

What it means

Raised by generate() in release/notes.py when the JIRA query `project=KAFKA and fixVersion={version}` returns an empty list, meaning no issues carry the requested fixVersion. The script (used to produce RELEASE_NOTES.html) treats a version with zero tagged issues as a configuration mistake rather than a valid empty release, so it aborts. It exists to prevent publishing release notes for a version string that does not match anything in JIRA.

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 c31c9215e1)

Solutions

  1. Verify the exact fixVersion label in JIRA at https://issues.apache.org/jira by browsing project KAFKA's released versions, and pass that exact string (e.g. `3.7.0`) to notes.py
  2. Confirm at least one issue is tagged with that fixVersion in JIRA; if the version exists but has no issues yet, assign issues or wait until release content is populated before running the script
  3. Check your network connection and that https://issues.apache.org/jira is reachable, since the JIRA() client is anonymous and an outage or empty paginated response makes query() return []
  4. If you are targeting a version that legitimately has no issues yet, decide whether to skip release-note generation for it or seed it with at least one issue before retrying

Example fix

// before
$ python release/notes.py 3.7 > RELEASE_NOTES.html
Didn't find any issues for version 3.7

// after
$ python release/notes.py 3.7.0 > RELEASE_NOTES.html

When it happens

Trigger: Running `python release/notes.py <version>` where <version> does not exactly match a fixVersion configured on any KAFKA JIRA issue. Also triggered by a typo, a missing dot release suffix (e.g. passing `3.7` when issues are tagged `3.7.0`), or a version that has not yet had any issues assigned to it in JIRA. Network/JIRA outage returning an empty result set from the search_issues pagination loop can also surface this, because query() would return [].

Common situations: Releasing a new minor line before any issues are tagged with that fixVersion; using the wrong version format (Kafka uses x.y.z, e.g. `3.7.0` not `3.7`); running the script against a fork or test JIRA project that has no KAFKA issues; JIRA being unreachable or the anonymous client being rate-limited so the search returns nothing; copy-pasting a version from a release plan doc that differs from the JIRA fixVersion label.

Related errors

AI-assisted analysis of apache/kafka@c31c9215e1 (2026-08-03). Data as JSON: /data/errors/630c96afcedd26d9.json. Report an issue: GitHub.