create-jira-ticket-with-reference

Name: create-jira-ticket-with-reference
Availability: InStock
Author: Akshat

Create Jira tickets by inheriting metadata from a reference ticket.

Updated Apr 6, 2026

Search Tags:#ticket management #Jira #ticket creation #CI/CD pipeline #metadata inheritance

Ready to run

npx skills add https://github.com/akshatdalton/skills --skill create-jira-ticket-with-reference

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-jira-ticket-with-reference
Source: https://github.com/akshatdalton/skills/tree/main/create-jira-ticket-with-reference
Command: npx skills add https://github.com/akshatdalton/skills --skill create-jira-ticket-with-reference

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires atlassian-mcp, jira, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the time-consuming task of manually entering ticket metadata by enabling users to create Jira tickets by inheriting metadata from a reference ticket.

Core Features & Use Cases

Metadata Inheritance: Automatically inherit metadata such as priority, sprint, labels, and pod from an existing Jira ticket.
User Overrides: Allow users to override certain metadata if needed.
Workflow Automation: Simplify the ticket creation process and reduce manual steps.

Quick Start

Use the create-jira-ticket-with-reference skill by providing the ID or URL of an existing Jira ticket. For example: "Create a ticket like ENG-12345 using ticket ENG-12345 as a reference."

Frequently Asked Questions about create-jira-ticket-with-reference

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

FAQPage Schema

How do I create a Jira ticket by copying metadata from an existing ticket?▼

To create a Jira ticket by inheriting metadata, provide the ID or URL of an existing reference ticket. The skill automatically copies priority, sprint, labels, and pod data while allowing manual overrides for specific fields.

Can I override inherited metadata when creating a Jira ticket from a reference?▼

Yes, you can override inherited metadata when creating a Jira ticket from a reference. While priority, sprint, and labels are copied automatically, the workflow allows you to manually specify custom values for certain fields.

What Jira permissions do I need to automate ticket creation using a reference ticket?▼

Automating Jira ticket creation with a reference ticket requires standard Jira API access and appropriate permissions to create and edit issues. The skill depends on the atlassian-mcp integration to interact with your Jira environment.

What's the best way to automate Jira ticket creation in a CI/CD pipeline?▼

Automating Jira ticket creation in a CI/CD pipeline is best handled by inheriting metadata from an existing reference ticket. This approach reduces manual entry steps by automatically copying sprint, priority, and labels from a known template issue.

Does this Jira ticket creation method support copying sprint and pod assignments?▼

Yes, this Jira ticket creation method supports copying sprint and pod assignments. It automatically inherits these fields from the reference ticket ID provided, streamlining workflow automation and reducing manual configuration overhead.