Jira Ticket Rewrite
Rewrite JIRA tasks to include key context, clear action items, and be easy for designers/developers to follow.
Prompt
Rewrite this JIRA task so it includes key context and clear action items and is easy for designers/developers to follow.
Original Ticket:
[Paste current JIRA ticket]
Provide:
1. Improved Ticket Structure
- Clear title
- Comprehensive description
- Well-organized sections
- Easy to scan format
2. Context Section
- Background and why this is needed
- Related work or dependencies
- User/business context
- Design system considerations
3. Clear Requirements
- What needs to be done
- Acceptance criteria (specific, testable)
- Design requirements
- Technical requirements
4. Action Items
- Step-by-step tasks
- Clear deliverables
- Dependencies
- Blockers
5. Design Specifications
- Design files or references
- Design system components to use
- States and variants needed
- Responsive considerations
6. Technical Notes
- Technical constraints
- Integration points
- API requirements
- Testing considerations
7. Resources & References
- Relevant design files
- Documentation links
- Related tickets
- Examples or inspiration
8. Definition of Done
- Clear completion criteria
- What needs to be delivered
- How to verify completion
- Handoff requirements
Format as a well-structured JIRA ticket ready to assign.How to use
- 1Copy your current JIRA ticket text (description, acceptance criteria, etc.)
- 2Replace [Paste current JIRA ticket] with your actual ticket text
- 3Add context before the prompt: Describe the ticket type and goals. Example: "This is a design system component ticket. Goal: Create a Button component with variants."
- 4If you have design files: Paste Figma links or design descriptions. Say "Design files: [paste links or describe]"
- 5If you have related tickets: Mention related tickets. Say "Related to: [ticket numbers or descriptions]"
- 6Paste the modified prompt into your preferred AI tool, like ChatGPT or Claude
- 7Review the improved ticket: Check context section, clear requirements, and acceptance criteria
- 8Verify completeness: Ensure all sections (design specs, technical notes, resources) are included
- 9Update your JIRA ticket: Copy the improved ticket structure back to JIRA
- 10Share with team: Use the improved ticket to ensure designers/developers have all context they need
Pro Tips
- • Include original ticket: Even if incomplete, paste the original so AI knows what exists
- • Specify ticket type: Mention "Design ticket" or "Development ticket" for appropriate structure
- • For design tickets: Include Figma links, design system references, and responsive requirements
- • For dev tickets: Include technical requirements, API details, and testing considerations
- • Request template: Ask "Create a JIRA ticket template based on this structure" for future tickets
