In my organization we are having a debate regarding the following topic: whether under the Summary field we are supposed to fill in the voice of the customer statement (As A User I Want X So that Y) or an actual summary of the story like Order Management?
I believe that the "As a User bla bla" statement should be filled in the Description field and not the Summary field, but some of my other colleagues are arguing that it should be in the Summary.
Is there an official response/good practice from the Atlassian community that can confirm 100% what should be written down in the Summary field of a user story?
It can be either.
I've seen teams utilise Summary for the user story, so that they can see it when utilising Story-based swimlanes on a board. These swimlanes show the sub-tasks below a story, but the Summary is visible along the top of the swimlane itself.
Other teams use Description so the story and the acceptance criteria can be listed together.
There's no right answer, but I prefer to use Description, mainly because:
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events