jira-task

Generate Jira tasks with Prowler's standardized format for bugs, features, and chores.

2|Updated Jun 11, 2024
One-click install
npx skills add https://github.com/gutierrezp22/administracion-departamentos --skill jira-task-gutierrezp22
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jira-task
Source: https://github.com/gutierrezp22/administracion-departamentos/tree/main/.cursor/skills/jira-task
Command: npx skills add https://github.com/gutierrezp22/administracion-departamentos --skill jira-task-gutierrezp22

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of Jira tasks by enforcing Prowler's standardized format for bugs, features, and other work items, ensuring consistency and clarity.

Core Features & Use Cases

  • Standardized Task Creation: Generates Jira tasks following specific templates for bugs, features, enhancements, refactors, docs, and chores.
  • Component-Based Structuring: Supports splitting multi-component work into separate, linked tasks (API, UI, SDK).
  • Use Case: When a bug is reported in the AWS provider UI, use this skill to create a Jira task with the correct format, including API and UI components, and link them appropriately.

Quick Start

Use the jira-task skill to create a bug ticket for the API component.

Frequently Asked Questions about jira-task

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

FAQPage Schema
How do I create a standardized Jira ticket for a bug or feature?

To create a standardized Jira ticket, use a template enforcing structured sections for description, acceptance criteria, technical notes, and testing. This ensures consistency for bugs, features, and other task types.

What is the proper format for splitting multi-component work into separate Jira tasks?

The proper format for multi-component work splits tasks by component, such as API, UI, or SDK. It generates separate linked Jira tickets to track distinct deliverables while maintaining structural consistency.

How do I structure acceptance criteria and technical notes in a Jira task?

You structure acceptance criteria and technical notes by enforcing specific sections within the Jira task template. This guarantees clarity and defined testing requirements for every generated issue.

Can I generate Jira tasks for refactoring, documentation, and chores using a standardized template?

Yes, you can generate Jira tasks for refactoring, documentation, and chores. The template enforces defined title conventions and priority guidelines across various issue types including enhancements.

Does this Jira task creation method enforce specific title conventions and priority guidelines?

Yes, this Jira task creation method enforces specific title conventions and priority guidelines. It adheres to defined standards to maintain clarity and consistency across all generated work items.

What are the limitations when generating Jira tasks for different issue types?

The limitation is that Jira tasks must strictly adhere to the predefined Prowler standard format. Deviating from the required sections for description, acceptance criteria, and technical notes breaks the structured output.