Using JIRA for Requirements Management
While JIRA has been developed primarily as an issue and project tracker out of the box, you can use JIRA for requirements management in conjunction with Confluence. We will review how Atlassian uses our products for this purpose, as well as provide some relevant resources for further information.
Atlassian uses a public instance for our requirements management through feature requests and voting on our public issue tracker.
For internal discussion, we use Confluence for general requirements gathering and project discussion on a Confluence page. We then utilize Confluence and JIRA's integration to create issues from those requirements pages; allowing us to view both the requirements content in line with the JIRA issues/tasks which correspond to the project. The wiki allows our developers to edit the requirements as needed while making it easy for developers and stakeholders to stay up to speed.
Issue Level Requirements
You're able to create a JIRA issue type specifically for requirements with its own workflow, custom fields and reporting. Sub-tasks offer a quick way to add and manage your requirements, and you can link related requirements together or with feature requests.
Confluence integrates seamlessly with JIRA, allowing you to track your requirements in JIRA, linked to your corresponding project documentation in Confluence. To facilitate documenting your requirements, Confluence ships with a Blueprint template for requirements writing: Product Requirements Blueprint.
Apps and Integrations with Other Tools
- R4J – Requirements Management for JIRA
- RMsis - A Requirement Management Extension for JIRA
- Wikidsmart (Requirements and Test Case Management)