Skip to content

Usage Examples

Terminal window
jtk issues create \
-P PROJ \
-s "Login button unresponsive on mobile Safari" \
-t Bug \
--priority High \
--labels "mobile,safari,regression"
Terminal window
jtk issues search "assignee = currentUser() AND status != Done ORDER BY priority DESC"
Terminal window
# Find your board
jtk boards list --project PROJ
# List active sprints
jtk boards sprints 42 --state active
Terminal window
# On branch feature/PROJ-123-oauth
jtk worklogs add --time 2h --comment "Implemented token refresh"
Terminal window
jtk issues get PROJ-123 --json | jq '.fields.status.name'
Terminal window
# On branch feature/PROJ-123-oauth
jtk issues transition "In Progress"
# Later...
jtk issues transition "Code Review"

These examples show what an AI agent can do when jtk is configured as an MCP server.

You: What’s left in the current sprint for board 42? Are we on track?

The AI will:

  1. Call manage_boards with get_active_sprint to find the active sprint
  2. Call manage_boards with get_sprint_issues to get all issues
  3. Summarize progress by status category

You: Create a high-priority bug in PROJ: “API returns 500 when email contains a plus sign”. Assign it to the user with email jane@example.com.

The AI will:

  1. Call manage_users with search to find Jane’s account ID
  2. Call manage_issues with create including the assignee_id

You: What’s the dev status of PROJ-100? Are there any open PRs?

The AI will:

  1. Call manage_issues with get to get issue details
  2. Call manage_devinfo with get_dev_info to get branches, PRs, commits
  3. Highlight any open PRs needing review

You: Generate release notes for PROJ version v2.0.0

The AI will use the release_notes prompt, which:

  1. Searches for all issues with fixVersion = "v2.0.0"
  2. Groups by issue type
  3. Formats as professional release notes

You: Find all bugs in PROJ that were created this week and show me the dev info for each.

The AI will:

  1. Call manage_search with JQL: project = PROJ AND issuetype = Bug AND created >= -7d
  2. For each result, call manage_devinfo with get_dev_info
  3. Present a summary table