Requirement against User Stories in 4.1

Wednesday, February 19, 2014

We have just installed Spira Team 4.1 on a test server to explore the new features. I have been wondering why "User Story" is a selection type for a Requirement.

In my organisation, Requirements are treated separately and User Stories and Acceptance criteria are written based on the requirements. In fact, I created a custom property called "User Stories" in Spira Team 4.0 to capture this as part of a requirement specification.

Can anyone throw some light on how they use "User Story" as a requirement type rather than being a separate entity in itself and what benefit this would have?

3 Replies
Thursday, February 20, 2014
re: praveens84 Wednesday, February 19, 2014
Hi Praveen

The main reason is so that you can define (if you want) a different workflow for a 'User Story' than other requirement types. In addition, you can then filter the Planning > Requirements list to only show user stories and not other requirement types (use cases, qualities, etc.)


Thursday, March 20, 2014
re: inflectra.sarahx Thursday, February 20, 2014
Ok so lets say you have requirements defined as User stories and you want to add use cases under the user story.
How do you do that?

If I try to do it in your demo project I just get the user store changed to a package where I then can add the use case under.
The problem is that I need to have spire to sync with Jira so I'm tryifng to figure out how much we need to change in our Jira workflow so they match.

Hope to hear from you soon.
Tuesday, July 29, 2014
re: AQLIVE Thursday, March 20, 2014
We also would benefit from being able to put requirements under user stories that do not change the user story into a "feature" artifact, removing the steps.

Spira Helps You Deliver Quality Software, Faster and With Lower Risk

And if you have any questions, please email or call us at +1 (202) 558-6885


  • Started: Wednesday, February 19, 2014
  • Last Reply: Tuesday, July 29, 2014
  • Replies: 3
  • Views: 9985