Verified:GitHub

jira-move

Transition Jira tickets from "In Review" to "Merged" after verifying GitLab MR merges.

Updated Aug 27, 2026

Search Tags:#automation #workflow #devops #jira #gitlab #tickets

One-click install

npx skills add https://github.com/swtch1/dotfiles --skill jira-move

Or copy as Structured Prompt for Agent▼

Please help me install this Agent Skill.
Skill: jira-move
Source: https://github.com/swtch1/dotfiles/tree/main/.claude/skills/jira-move
Command: npx skills add https://github.com/swtch1/dotfiles --skill jira-move

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of moving Jira tickets from "In Review" to "Merged" status once all associated GitLab merge requests have been successfully merged, reducing manual tracking and status updates.

Core Features & Use Cases

Automated Jira Ticket Transitioning: Moves tickets in bulk based on external repository status.
GitLab MR Status Check: Verifies the merge status of associated GitLab merge requests.
Use Case: After a development sprint concludes, use this Skill to automatically update all relevant Jira tickets to "Merged" status, reflecting the completed work and merged code.

Quick Start

Automatically move my Jira tickets from "In Review" status to "Merged" status when all their associated GitLab merge requests have been merged.

Frequently Asked Questions about jira-move

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automatically transition Jira tickets to Merged status after GitLab merge requests are merged?▼

To automatically transition Jira tickets to Merged status, this Skill verifies the merged state of associated GitLab merge requests extracted from ticket comments and bulk transitions eligible tickets from In Review to Merged. It targets tickets assigned to you within open sprints and provides a summary of actions taken.

How does automated Jira ticket transitioning based on GitLab merge request status work?▼

Automated Jira ticket transitioning works by extracting GitLab MR URLs from Jira ticket comments, checking the MR merge statuses in parallel, and moving tickets from In Review to Merged only when all associated merge requests are confirmed merged.

Can I bulk update Jira tickets assigned to me in open sprints based on external repository status?▼

Yes, you can bulk update Jira tickets assigned to the current user within open sprints. The Skill checks the merge status of associated GitLab merge requests in parallel and transitions all eligible tickets accordingly.

What is the best way to sync Jira ticket status with merged GitLab merge requests after a sprint?▼

The best way to sync Jira ticket status with merged GitLab merge requests after a sprint is to use this automation Skill, which verifies MR statuses in parallel and bulk transitions tickets from In Review to Merged, reducing manual tracking and status updates.

Do I need to manually link GitLab merge requests to Jira tickets for this automation to work?▼

You do not need to manually link them outside of Jira, but the Skill requires GitLab MR URLs to be present in the comments of the Jira tickets. It extracts these URLs from the comments to verify the merge status of each associated merge request.

What happens if not all GitLab merge requests associated with a Jira ticket are merged?▼

Jira tickets are only transitioned from In Review to Merged when all associated GitLab merge requests have been successfully merged. If any MR is not merged, the ticket remains in its current status and is included in the action summary.