Back to Forum

What is the best practice to place user story in JIRA

Last post 12:46 am February 20, 2019 by Jalal Adeli
4 replies
Jalal Adeli
04:28 pm February 13, 2019

Hello,

 

I just wanted to know what is the best practice to write user story in JIRA. Should it go in the summery /title or description. Your input is greatly appreciated.

 

Jalal  

Nils Hyoma
08:18 pm February 13, 2019

Hi Jajal,

you should decide with your team together. 

Mike Cohn is talking in his video [1] about the 3 Cs: Card, Conversation, Confirmation. So you should find a way to document your results in Jira as a team.

I, personally, would put the story in the description.

Nils

[1] https://www.mountaingoatsoftware.com/presentations/introduction-to-user…

 

Daniel Wilhite
08:21 pm February 13, 2019

@Nils is correct with his statement of ask your team.  There is no correct way to do it.  Do what works best for your team regardless of what you read on the internet. 

Chris Belknap
12:00 am February 14, 2019

What I typically see is a brief description in the Summary field, and more details in the Description field, with the ubiquitous user story format in the Description Field because there is more space.

But as others stated, there's no best way and it's worth a conversation with your Scrum Team.

Jalal Adeli
10:05 pm February 15, 2019

Thank you all for your input. It is appreciated.

By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.