[Sentry01]

Agent assessment

Self-reported assessment, not an independent review.

Assessed revision: 35ec3256e5b3d5e18825a2bd3422a2c17a1bdfea

Dimension	Assessment	Rationale
Change confidence	8/10	The listing matches the release tag and upstream plugin quality checks passed; the license check timed out and maintainer review remains.

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension file in the correct directory.
• The file follows the required naming convention.
• The content is clearly structured and follows the example format.
• I have tested my instructions, prompt, agent, skill, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

Version update for the already approved jira-workbench external plugin (submission #5134, listed in #5859). Awesome Copilot's CONTRIBUTING.md describes quality checks for updates to listed external plugins.

The existing entry in plugins/external.json pins version, source.ref and source.sha to the selected release and its tag commit. .github/plugin/marketplace.json was regenerated with npm run build, and npm run plugin:validate passed. No other fields change.

The initial update moved the listing from 2.1.3 to 2.4.2; later commits may supersede it. See the diff for the current pin and the release notes.

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• Other (please specify):

---

Additional Notes

I am the plugin author. Future releases will arrive as similar version-only update PRs. Please let me know if maintainers prefer a different route for listing updates.

---

By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

[github-actions]

🚦 Submission status: ✅ Approved

Risk tier: merge-risk:high — Privileged execution, automation, or review-policy change
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access, including a maintainer with admin or maintain permission.

Why this tier

• plugins/external.json is a high-risk path (automation, scripts, MCP config, hooks, or review policy)

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Plugin and extension validation	✅ Passed	Passed · logs
Plugin structure	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs
Canvas/plugin smoke test	✅ Passed	Passed · logs

Review

• Approvals: 1/1 (aaronpowell)
• Assigned reviewer: not assigned yet — comment /request-review to ask for one
• Review target date: not set
• The core-maintainers pool is not staffed yet; an approver with admin or maintain permission is required instead.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 35ec325 · gate run · This comment is maintained automatically — see submission gate docs.}

[github-actions]

🔒 PR Risk Scan Results

Scanned 2 changed file(s).

Severity	Count
🔴 High	0
🟠 Medium	0
ℹ️ Info	0

✅ No matching risk patterns were detected in changed files.

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🛑 External plugin PR checks failed (maintainer follow-up)

• Changed entries detected: 0

• Workflow state label: ready-for-review

• Status legend: ✅ pass · ⚠️ warning · 🛑 fail

Per-plugin quality summary

Plugin	spec compliance	vally lint	install smoke test	version match	ref/sha consistency	canvas structure	overall	source tree
none	⚪ not_run	⚪ not_run	⚪ not_run	⚪ not_run	⚪ not_run	⚪ not_run	⚪ not_run	n/a

External plugin PR change detection failed unexpectedly. Re-run this workflow.

[Copilot]

🔵 Needs a closer look

Because v2.4.2 modifies executable upstream canvas code, the external-plugin manifest, pinned ref/SHA, install smoke test, and canvas quality gates still require confirmation before merge.

No open issues 🎉

What changed in this PR

Updates the approved jira-workbench external plugin listing from version 2.1.3 to 2.4.2, with the generated marketplace metadata synchronized to the pinned release.

Changes:

• Updates the plugin version to 2.4.2.
• Pins the source to tag v2.4.2 and commit e1f47f5912e0850e30aae76719ffd0f6de7abcd4.
• Regenerates the marketplace entry with matching metadata.

File	Description
plugins/​external.json	Updates the canonical external plugin version and immutable source revision.
.github/​plugin/​marketplace.json	Synchronizes the generated marketplace metadata with the updated release.

_{Review effort: Lite (auto)}

[Sentry01]

/rerun-checks

[github-actions]

🔁 /rerun-checks for 35ec325

Re-running: Submission Gate.

The status comment updates when the checks finish.

[aaronpowell]

Thanks for keeping the jira-workbench listing current. This is a version-only update to the already-approved listing: plugins/external.json and the regenerated .github/plugin/marketplace.json both move to 2.4.2, and tag v2.4.2 resolves to the pinned commit e1f47f5. The external plugin checks (spec compliance, install smoke test, version match, ref/SHA consistency and canvas structure) all pass. The License compliance check failure is a timeout rather than a license finding, so it just needs a re-run. Opening future releases as similar version-only PRs works well.

[Sentry01]

@aaronpowell I think the license compliance keep failing and blocks the merge, I couldnt find a way to rerun that job.

[Copilot]

🔵 Needs a closer look

Approval should wait for maintainer review of the upstream v2.4.2 runtime/UI, documentation, and test changes and completion of the unresolved license check.

No open issues 🎉

_{Review effort: Lite (auto)}