Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Best practice to mark a story as "specified"?

In our project the product owner has to fill the backlog with stories, which will be taken by the developers and planned for sprints.

The developers want to be sure they plan only fully specified stories and the product owner wants to be sure he marks each story that is ready as "specified".

Which is the best practice to do this? Should I

a: use the "Resolution" field to include a "specified" value or

b: include a new "status" field into the story definition or

c: should I define a specification board in addition to my board with a workflow like "to do -> in progress -> specified" 

d: or is there another best practice for solving this problem? 

 

 

2 answers

0 votes

Hi @Anar Chipur ,

It actually depends on you, which of the above solutions work best for you.

All the above 3 solutions described by you can fulfill the need.

However, creating a new board will bring more effort for the entire team as compared to the other two options.

In my organization we have a similar workflow and we use the "status" field to mark the story as "specified". We haven't faced any issues till now.

So you can go ahead with the Status field :-)

Thank you @Deepanshu Natani !

I actually want that the product owner team to know which stories are "specified" and are ready for sprint planning. So they need to mark the stories as "draft" and "specified".

How can I use the status field to mark a story a story? As far as I know I have to define this status in my workflow first... Is this correct..? 

However, I do not want to have this status in my sprint board, I just want that it is visible for the product owner team working in the backlog... 

So, do I need to define the statuses "draft" and "specified" in my workflow in order to set the "status" field? 

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

118 views 7 9
Read article

Community Events

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

Events near you