You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
Hi @Claire_De_Cort ,
Jira Align's Story Point field (also shown as LOE or Level of Effort on various screens) assumes an INTEGER input (as of me writing this reply).
There is no rounding, therefore you get interesting results.
Teams should never use less than one story point (or decimal values) if they are agile (half points are not agile).
I recommend to all my clients putting a mask on the Jira story point field to provide a drop down of Fibonacci values (1,2,3,5,8,13) or at least setting the field to integer values.
PS: @Tim Keyes - Any additional insights?
Hi Peter and Claire,
The connector will round the story point value as it comes in from Jira to the nearest whole number. 1.49 in Jira would become 1.0 in Jira Align and 1.51 in Jira would become 2.0 in Jira Align.
Some type of effort to create consistency between the two applications as Peter suggested is a great idea.
Jira Align will force the 0 or 1 point estimate.
Hi @Tim Keyes,
I was told by Shak Align only stores integer values. So it wouldn't round to 1.0 or 2.0, it would actually round and truncate to 1 and 2, correct? The distinction is important.
Please correct me if I'm wrong.
Just tested this:
Jira stories with 0.5 points or fewer will appear in Jira Align with 0 LOE.
Jira stories with greater than .5 points will appear in Jira Align with 1 LOE.