jira-ticket

Create Jira issues from plain-language developer descriptions for the SAAS project.

3|7|Updated Nov 7, 2025
One-click install
npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-ticket-dimagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-ticket
Source: https://github.com/dimagi/dimagi-claude-workflows/tree/main/plugins/commcare-tech/skills/jira-ticket
Command: npx skills add https://github.com/dimagi/dimagi-claude-workflows --skill jira-ticket-dimagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduce the friction of creating consistent, well-formed Jira issues in the SAAS project by turning a free-form developer description into a prioritized, sprint-assigned ticket with smart defaults and minimal user effort.

Core Features & Use Cases

  • Smart defaults: always sets project SAAS with team-specific Cloud ID and known custom field keys.
  • Assignee resolution: detects named assignees via lookup, defaults to the authenticated user, and respects explicit "unassigned".
  • Issue type & effort inference: infers Task/Improvement/Bug/Performance/Story and maps natural language to the required effort field options.
  • Epic & sprint handling: links to an epic when provided or asked, searches open sprints with JQL and assigns to Product or Platform sprints based on content, and transitions newly prioritized sprint tickets when applicable.
  • Priority & description rules: only sets priority when stated, creates concise summaries following team conventions, and writes descriptions only when extra detail is given.
  • Confirmation output: returns a compact post-creation summary with ticket URL, sprint or Backlog, effort, and assignee.

Quick Start

Create a SAAS Jira ticket by describing the work in plain English, for example: /jira-ticket investigate formplayer memory spikes, assign to Graham.

Frequently Asked Questions about jira-ticket

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

FAQPage Schema
How do I create Jira tickets from plain English descriptions?

You can create Jira issues from plain English by providing a developer description. The skill infers issue type, effort, priority, epic, and sprint, then calls createJiraIssue to generate the ticket in the SAAS project with minimal input.

Can I assign a Jira ticket to a specific person using natural language?

Yes, you can assign Jira tickets using natural language by including a name in the description. The skill resolves the assignee via name lookup, defaults to the authenticated user if no name is given, and respects explicit "unassigned" requests.

How does natural language sprint assignment work in Jira?

Natural language sprint assignment works by searching open sprints with JQL based on your description. The skill determines Product or Platform sprint intent, sets the sprint custom field (customfield_10010), and optionally transitions the issue when assigned to a sprint.

What issue types and effort levels can be inferred when creating Atlassian tickets?

When creating Atlassian tickets, the skill infers issue types including Task, Improvement, Bug, Performance, and Story. It maps your natural language description to the required effort field options (customfield_10160) for properly formatted issues.

Do I need to specify a priority when creating a Jira issue from text?

No, you do not need to specify a priority when creating a Jira issue from text. The skill only sets the priority when explicitly stated in your description, otherwise relying on smart defaults to generate the ticket.

What happens if no assignee is mentioned in the Jira ticket description?

If no assignee is mentioned in the Jira ticket description, the skill defaults to the authenticated user. It also respects explicit "unassigned" requests, ensuring the ticket is created with the correct assignee based on your input.