finalize-sus

Automating Jira issue transitions and time tracking after a fix requires coordinating status updates, standardized comments, and timesheet logging. This Skill handles post-fix closure by transitioning issues to Ready to Review or Done, adding PR URLs, and logging hours via internal endpoints.

To automate Jira task closure with PR validation, you need a task key, date, start time, PR URLs, a summary, and a list of changed repositories. These inputs drive the workflow to post standardized comments, validate PRs, transition the issue status, and record learned patterns.

Yes, you can transition Jira issues without a linked pull request for analysis-only scenarios. The workflow supports both SUS tasks with associated PRs and scenarios requiring only issue comments, status transitions, and timesheet entries without code changes.

Automated Jira commenting handles multiple repository changes by standardizing the comment format to include all provided PR URLs and affected repositories. This ensures the Jira issue accurately reflects every repository modified during the fix.

The best way to log hours while transitioning an issue to Done is to automate the timesheet entry alongside the status change. This Skill coordinates the Jira status transition with internal time-tracking endpoints to record hours and save learned patterns simultaneously.