consigcody94/ticket-tamer

🎫 Ticket Tamer

AI-powered Jira project management - create issues, search with JQL, manage epics, add comments, and transition workflows

🤔 The Project Management Challenge

"Jira context switching disrupts my development flow"

Every bug report, status update, or sprint check requires leaving your IDE and navigating through Jira's UI.

• 🖱️ Clicking through issue forms
• 🔍 Writing JQL queries manually
• 📋 Managing workflow transitions
• 💬 Adding comments across issues

Ticket Tamer brings Jira to your conversation - create issues, search backlogs, and manage workflows without leaving your editor.

✨ Features

🚀 Quick Start

Prerequisites

• Node.js 18+
• Jira Cloud, Server, or Data Center instance
• API token or credentials
• Claude Desktop

Installation

git clone https://github.com/consigcody94/ticket-tamer.git
cd ticket-tamer
npm install
npm run build

Get Your API Token

Jira Cloud:

1. Log in to Atlassian
2. Click "Create API token"
3. Give it a label and create
4. Copy the token

Jira Server/Data Center:

1. Log in to your Jira instance
2. Go to Profile → Personal Access Tokens
3. Create a new token
4. Copy the token

Configure Claude Desktop

Add to your config file:

{
  "mcpServers": {
    "ticket-tamer": {
      "command": "node",
      "args": ["/absolute/path/to/ticket-tamer/dist/index.js"]
    }
  }
}

Restart Claude Desktop

Completely quit and reopen Claude Desktop to load the MCP server.

💬 Usage Examples

Create Issues

"Create a high-priority bug for the login issue"
→ Creates Bug issue with priority High in specified project

"Add a story for implementing OAuth2 authentication"
→ Creates Story with detailed description and acceptance criteria

Search Your Backlog

"Find all my in-progress issues"
→ Runs JQL: assignee = currentUser() AND status = "In Progress"

"Show high-priority bugs in the PROJ project"
→ Runs JQL: project = PROJ AND type = Bug AND priority = High

Manage Workflow

"Move PROJ-123 to Done"
→ Transitions issue through workflow to Done state

"Add a comment to the deployment issue"
→ Adds comment with deployment notes

Organize with Epics

"Create an epic for the authentication overhaul"
→ Creates Epic with name and description for organizing stories

🛠️ Available Tools

📊 Tool Details

create_issue

Create a new Jira issue.

Config object:

update_issue

Update an existing issue.

Common fields:

• summary - Issue title
• description - Issue description
• priority - { "name": "High" }
• assignee - { "accountId": "..." }
• labels - ["label1", "label2"]

search_issues

Search issues using JQL.

create_epic

Create an Epic issue.

add_comment

Add a comment to an issue.

transition_status

Transition an issue to a different status.

🔍 JQL Query Reference

Basic Queries

Date Queries

Combined Queries

Ordering

🎯 Workflow Examples

Bug Triage

1. Create the bug:

   create_issue with projectKey: "PROJ", summary: "...", issueType: "Bug", ...
   

2. Add details via comment:

   add_comment with issueKey: "PROJ-123", comment: "Additional info: ..."
   

3. Assign and start:

   update_issue with issueKey: "PROJ-123", fields: {assignee: {...}}
   transition_status with issueKey: "PROJ-123", transitionName: "In Progress"
   

Sprint Planning

1. Search backlog:

   search_issues with jql: "project = PROJ AND sprint is EMPTY ORDER BY priority"
   

2. Create epic for feature:

   create_epic with projectKey: "PROJ", summary: "...", epicName: "Q1-Feature"
   

Issue Resolution

1. Add resolution comment:

   add_comment with issueKey: "PROJ-123", comment: "Fixed in commit abc123"
   

2. Close issue:

   transition_status with issueKey: "PROJ-123", transitionName: "Done"
   

🔒 Security Notes

🐛 Troubleshooting

📋 Requirements

• Node.js 18 or higher
• Jira Cloud, Server, or Data Center instance
• API token or credentials

🤝 Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

📄 License

MIT License - see file for details.

👤 Author

consigcody94

Tame your tickets, unleash your productivity.