cars-project

name	cars-project
version	1.1.0
user-invocable	false
description	CARS project-specific configuration for the carscommerce.atlassian.net org. Activated automatically by /jira-create when the user is working in the CARS project. Provides work hierarchy, issue type names, team field setup, and UUID resolution instructions specific to carscommerce.

CARS Project Configuration

This skill is activated by /jira-create when the authenticated user's Atlassian site is carscommerce.atlassian.net and the user selects the CARS project. It provides the custom field IDs and value formats specific to this org.

Work Hierarchy

The CARS project uses the following hierarchy from highest to lowest:

Objective
  └── Initiative
        └── Epic
              └── Story / Bug / Task
                    └── Sub-Task

Level	Jira issue type name	Skill
Objective	Objective	create-jira-objective
Initiative	Initiative	create-jira-initiative
Epic	Epic	create-jira-epic
Story	Story	create-jira-story
Bug	Bug	create-jira-bug
Task	Task	manage-jira (generic)
Sub-Task	Sub-task	manage-jira (generic)

When creating a ticket, use the exact issue type name from the "Jira issue type name" column above in atlassian___createJiraIssue.

Custom Field IDs

Field	Custom field ID	Value format
Team	customfield_11100	Plain string UUID
Sprint	customfield_10007	Plain integer ID
Story Points	customfield_10004	Numeric value

Post-Creation Steps

Every ticket created in the CARS project must have a team assigned to appear on the board. Immediately after the ticket is created by a create-jira-* skill, follow the team assignment steps below.

Team Field

Resolving a Team UUID

To find the UUID for a given team, fetch an existing ticket that already belongs to that team:

atlassian___getJiraIssue(cloudId, issueIdOrKey: "CARS-<existing-ticket>")

Look at the customfield_11100 field in the response. The value is the team UUID (a plain string, not wrapped in an object).

Setting the Team

After creating the ticket, set the team via atlassian___editJiraIssue:

atlassian___editJiraIssue(
  cloudId,
  issueIdOrKey: "CARS-<new-ticket>",
  fields: {"customfield_11100": "<team-uuid>"}
)

Pass the UUID as a plain string. Do not wrap it in {"id": "..."} -- that returns a 400 error.

Determining Which Team to Use

1. If the ticket has a parent, fetch the parent and read its customfield_11100.
   • If set, offer the user the option to inherit the parent's team or specify a different one via AskUser.
   • If not set, ask the user which team should own this ticket.
2. If there is no parent, ask the user which team should own this ticket.

Sprint Field

To find the sprint ID, view an existing ticket in the target sprint and read customfield_10007. It contains an array of sprint objects -- use the id from the active sprint object.

atlassian___editJiraIssue(
  cloudId,
  issueIdOrKey: "CARS-<new-ticket>",
  fields: {"customfield_10007": <sprint-id-integer>}
)

Pass the sprint ID as a plain integer. Do not wrap it in {"id": ...}.

Story Points Field

atlassian___editJiraIssue(
  cloudId,
  issueIdOrKey: "CARS-<new-ticket>",
  fields: {"customfield_10004": <points>}
)