JIRA Ticket in Template Format

Daniel Okoye

@daniel-okoye

·December 31, 2025

Create a JIRA ticket following exact template format.

20 copies0 forks

Share this prompt:

Create a JIRA ticket for this work.

Work description:
{{work_description}}

Constraints:
- Title: max 80 characters, action-oriented
- Description sections: Summary, Acceptance Criteria, Technical Notes
- Summary: 2-3 sentences
- Acceptance Criteria: 3-5 checkboxes using [ ]
- Technical Notes: bullet points for implementation hints
- Labels: suggest 2-3 relevant labels
- Story points: estimate using Fibonacci (1,2,3,5,8,13)

Output in exact JIRA-pasteable format.

Details

Category

Productivity

Use Cases

JIRA ticket creationWork item standardizationBacklog documentation

Works Best With

claude-opus-4.5gpt-5.2gemini-2.0-flash

Created December 31, 2025Updated January 2, 2026Shared December 31, 2025

Related Prompts

QBR Action Item Tracker Template

by @aisha-bello

Output-format template for documenting and tracking QBR action items.

Test Plan Generator from Idea (technical)

by @levi-smith

Generates a structured, production-ready test plan from an idea, with placeholders for project context and compliance, delivered as a machine-readable JSON.

Test Plan Generator from Idea (technical)

by @levi-smith

Generates a structured, production-ready test plan from an idea, with placeholders for project context and compliance, delivered as a machine-readable JSON.

Test Plan Generator from Idea (technical)

by @levi-smith

Generates a structured, production-ready test plan from an idea, with placeholders for project context and compliance, delivered as a machine-readable JSON.

Test Plan Generator from Idea (technical)

by @levi-smith

Generates a structured, production-ready test plan from an idea, with placeholders for project context and compliance, delivered as a machine-readable JSON.

Test Plan Generator from Idea (technical)

by @levi-smith

Generates a structured, production-ready test plan from an idea, with placeholders for project context and compliance, delivered as a machine-readable JSON.

More from @daniel-okoye

Product Engineer Feature Design

Technical Estimate Accuracy Review

Dependency Upgrade Risk Assessment

Postmortem Analysis Quality Check

Create your own prompt vault and start sharing