jira-create_skill

This skill helps you create properly formatted JIRA tickets for AG Charts, guiding bug, feature, and debt tasks with required fields.

TypeScript

433

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill ag-grid/ag-charts --skill jira-create

SKILL.md5.4 KB

Overview

This skill creates JIRA tickets that follow AG project conventions for Charts (and Grid with small changes). It guides you through bug reports, feature requests, improvements, tech-debt, and docs tickets with required fields, templates, and formatting rules. Use it when you want a ready-to-create, properly formatted JIRA payload.

How this skill works

The skill asks which ticket type you need, collects the required details (repro steps, expected vs actual, requirements, or proposed solution), and fills the appropriate template. It produces a JSON payload ready for the mcp__atlassian__createJiraIssue API call, including project key, summary prefix, components, track field, and any bug-specific fields like versions.

When to use it

When you ask “create a JIRA”, “file a bug”, or “write up a ticket”.
When you have a reproducible bug and need a properly formatted bug report.
When requesting a new feature or improvement with acceptance criteria.
When logging tech-debt or housekeeping tasks for Charts or Grid.
When you need a JIRA payload ready for automated creation via MCP.

Best practices

Always select the correct ticket type (Bug, Feature Request, Improvement, Housekeeping, Doc change).
Use the provided templates for description format; don’t improvise.
Start the summary with the correct prefix: [Charts] or [Grid].
Include markdown-formatted links for URLs and end numbered list items with periods.
For bugs: test in a browser and include Affects Version and a reproduction URL.

Example use cases

File a reproducible bug with steps, affected versions, and expected vs actual behavior for AG Charts.
Create a feature request that includes requirements, use cases, and acceptance criteria.
Log a tech-debt ticket describing context, problem statement, proposed solution, and acceptance criteria.
Create an improvement ticket to enhance an existing API or UI behavior with suggested API design.
Prepare a docs change ticket that points to the exact documentation section and required edits.

FAQ

Always use projectKey "AG". Use components [{"name":"Charts"}] for Charts tickets and [{"name":"Grid"}] for Grid tickets.

What fields are required for a bug ticket?

Required fields: issueTypeName (Bug), summary starting with [Charts] or [Grid], description using the bug template, components, custom track field, and Affects Version (versions).