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.
Due to recent challenges of most companies having to move to virtual and remote PI planning events, the Jira Align Solutions Architects wanted to start to capture some best practices and FAQ Table of...
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