[text-auditor] Batch fix misleading Bitbucket credential labels and benchmark/help text

[github-actions]

Text Improvements

The following user-facing text issues were found in the repository. Each is a low-effort fix.

1. Bitbucket credential descriptions incorrectly refer to JIRA

File: packages/atlassian_bitbucket/data_stream/audit/manifest.yml (line 72)
Current text: JIRA Username. Needs to be used with a Password. Do not fill if you are using a personal access token.
Suggested fix: Bitbucket Username. Needs to be used with a Password. Do not fill if you are using a personal access token.
Why: This is the Bitbucket integration and the field title is Bitbucket Username; JIRA Username is misleading.

File: packages/atlassian_bitbucket/data_stream/audit/manifest.yml (line 79)
Current text: JIRA Password. Needs to be used with a Username. Do not fill if you are using a personal access token.
Suggested fix: Bitbucket Password. Needs to be used with a Username. Do not fill if you are using a personal access token.
Why: Same terminology mismatch as above.

2. CLI message in testsreporter is awkward/ungrammatical

File: dev/testsreporter/testsreporter.go (line 61)
Current text: Skip creating GitHub issues, hit the maximum number (%d) of tests to be reported. Total failing tests: %d.
Suggested fix: Skipping GitHub issue creation: reached the maximum number (%d) of tests to report. Total failing tests: %d.
Why: The current sentence structure is awkward and unclear in user-facing output.

3. Rally benchmarks doc link points to pipeline benchmark page

File: docs/extend/elastic-package.md (line 61)
Current text: - [Rally benchmarks](https://github.com/elastic/elastic-package/blob/main/docs/howto/pipeline_benchmarking.md)
Suggested fix: - [Rally benchmarks](https://github.com/elastic/elastic-package/blob/main/docs/howto/rally_benchmarking.md)
Why: Link label and target topic do not match; users clicking Rally docs are sent to pipeline benchmarking docs.

Suggested Actions

• Replace the two JIRA credential descriptions in the Bitbucket audit manifest with Bitbucket wording.
• Rewrite the testsreporter max-threshold message to a grammatically clear sentence.
• Update the Rally benchmark link target in docs/extend/elastic-package.md to the Rally benchmarking page.

Note

🔒 Integrity filter blocked 6 items

The following items were blocked because they don't meet the GitHub integrity level.

• #17997 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #17994 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #17515 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #17997 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #17515 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #17994 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: Text Auditor

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

• expires on May 5, 2026, 10:49 AM UTC