How best to capture requirements/do requirements traceability, with NO Confluence and NO Requirement

[Kitty Holloway]

Hi, my company are wanting to use Jira to capture requirements (currently on spreadsheets…). However, we don’t have Confluence (apparently it has been ruled out by security)-and we currently don’t have issue type Requirements (I know that requirements are user stories, but not sure if we need that ticket type). Any suggestions on how best to do this?

[Nikola Perisic]

Welcome @Kitty Holloway 

You can create a work item type of Requirements, create a new work item scheme and then add the Requirements to it. What you can use for the requirements are forms in Jira, that you can share with your stakeholders. This is, if we are talking about the Cloud. 

Jira software form - limited in terms of fields

Jira service management form - has more options for the field creation

[Kitty Holloway]

Hi Nikola, many thanks for your reply. We are on Jira Cloud.  I think there will be resistance from my company for setting up Requirement ticket type, as the company is fairly early on the agile ways of working journey-and understandably, they are trying to get the message over to the business that requirements are a user story.

is there a way to do this without requirement ticket type? Or would you advise that it would be much easier if we did have that? I’m happy to build an argument for adding this-but need to go armed with information!

I have never used Jira forms-could u point me in the direction of where I can explore this?

[Nikola Perisic]

Hi @Kitty Holloway 

Ah, so the team is new to Agile. I would first introduce them to both Scrum and Kanban. You don't really need the requirement type, you can stick to the traditional stories and tasks. Make sure they understand the concept of user stories (acceptance criteria and more). 

For forms in software projects, you can find more info here: https://community.atlassian.com/forums/Jira-articles/A-new-way-to-manage-intake-in-Jira/ba-p/2856309