Topic
- Project Planning & Scheduling
Featured Apps
Table of Contents
Overview
Business Analysts and Product Owners often capture requirements and acceptance criteria in Jira issues. While descriptions and custom fields work for basic needs, they can become cluttered or unstructured. Some teams also use Confluence for detailed requirement documents.
Excel-like Tables for Jira helps bridge the gap by allowing requirement matrices directly inside a Jira issue, keeping acceptance criteria structured and actionable.
Scenario: Managing acceptance criteria or requirement matrices
Jira native
- Requirements and acceptance criteria are typically listed in plain text.
- Confluence pages provide detailed requirement documents, but they are not always connected back to Jira issues.
With Excel-like Tables for Jira
- Create a table inside an Epic or Story with fields like Requirement, Priority, Test Condition, and Status.
- Add formulas for scoring (e.g., Business Value ÷ Effort).
- Use Jira field mapping to link table values with Priority or Status fields.
Value
Makes acceptance criteria easier to manage inside Jira, while still allowing Confluence to remain the home for larger requirement documents.
