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

Your Points Tracker
  • 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
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?
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

Which value should I add in the Story Point field for User stories

Hi Jira team,

I am a new scrum master and trying to understand the relation between the agreed value in planning pocker technique(per example 40 or 1/2,etc) and the Story point field value in jira User stories/tasks.

Should I add in the Story Point field the value that we acceptd all as a team estimation for a user Story from the pocker cards (per example if the team had been agreed for 13 we write 13 as a Story Point value) or should we add in the story point field an estimation of the work to be done by taking on consideration the choosen card number(per example for 13 card's value=>3days of work).

Thanks a lot for help.

1 answer

1 accepted

3 votes
Answer accepted

Hi @amira bouali ,

Welcome to the community. 

You should put the estimation you accepted as team there.

The reason to usually use story points is not to use the time estimation for planning.

If you want to track against an time estimation, you should use original and remaining estimation. 

Thanks Sir for your reply can you explain to me please what do you mean by this point "If you want to track against an time estimation, you should use original and remaining estimation."

Jira does also have a time tracking built in. If that is enabled, you have two fields, Original estimate and remaining estimate. 

You could put a time estimation like 3days in there and everytime  you work on the issue, you log some work and the remaing estimate will be decreased until it reaches zero. If the remaining estimate is zero, the issue should be resolved. 

Like # people like this

Thanks a lot Sir for help.

Other question if you could help me please,how can I check the time tracking for each sprint?

I think, the Sprint report will help you most for that. 

Or, if you are using story points and want to know how much you have done in the past, the Velocity Report.

Like amira bouali likes this

Thanks Sir for you reply.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Marketplace Apps & Integrations

Why everyone using Jira must be GDPR-compliant

Did you know that penalties up to 4 % of the yearly company turnover are possible in case of GDPR violations? GDPR regulations are currently mainly relevant for companies in the EU, but countries lik...

53 views 0 0
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