mark-ticket-as-done

To transition Jira tickets to done, this Skill applies workflow transitions by name after PRs are opened, posting an exhaustive stakeholder comment linking every related PR. It resolves the tracker type and target status at runtime to ensure accurate end-to-end ticket closure preparation.

You can update GitHub Projects v2 status fields automatically after opening a pull request. The Skill validates your project configuration and updates the Status field option by name, ensuring consistent state transitions across your repositories.

Posting stakeholder comments linking multiple PRs during a Jira ticket workflow transition involves converting markdown to Atlassian Document Format. The Skill generates a comment containing the ticket summary, affected features, verification steps, and a mandatory list of every involved PR.

Yes, this ticket workflow automation supports idempotency by validating state and preventing replay on already-transitioned Jira or GitHub issues. It confirms the ticket, target status, PR links, and comment type before executing any status updates or posting comments.

Automating Jira and GitHub ticket status transitions requires installing gh, acli, marklassian, jq, and node. These dependencies facilitate CLI interactions, Atlassian Document Format conversion, JSON parsing, and runtime execution for staged automation across platforms.

The best way to ensure consistent ticket closure preparation across multiple repos is using staged automation with label-first status updates. This approach applies additive updates and validates existing project workflow configuration before writing changes to Jira or GitHub Projects v2.