I've got a plan in JIRA Portfolio tied to many JIRA projects. Today I did an 'update from date..."
It seems that for many JIRA issues were updated with incorrect original and remaining estimates.
I did not think what I was doing would push any updates from JIRA Portfolio or change any estimates.
I DID NOT do a "planned update to project(s)..."
Under plan config, data, sync: Update estimates is set to off.
Under keep backlog items in sync, Summary, Description, and Estimates fields were checked. Did having estimates checked cause this?
In short, my goal is to only go in one direction - Bring updates from JIRA to JIRA Portfolio (not vice versa).
I only want to update the work logged, status change, and progress. I don't care about updating the estimate if it might cause issues like this.
Can anyone advise?
Same issue happening to us - Portfolio "Update from date" is editing the "Original Time estimate" (e.g. adding 32 mins or so) in JIRAs and setting the "Remaining Time Estimate" to the same value as the Original Time Estimate - which makes it look like the JIRA still has it is affecting the JIRA sprint burndowns - but we need to "Update from date" in portfolio in order to accurately predict plans from here forward.
Note: as recommended in https://confluence.atlassian.com/jiraportfoliocloud/regular-plan-updates-715263783.html - we are using the date of the last sprint:
"If you are working with iterations, it is recommended that you use the planned start date of the upcoming sprint as the update date."
Can you explain why the start date of the next planned sprint must be used?
Note: we did initially think the adjustment of time was related to different number of hours set in JIRA (8h) and Portfolio (7.5h) - but these are now set to 8h.
What I've noticed is that doing "update from date" in portfolio that includes a story which has a sub-task causes the sub-tasks remaining estimate to be accumulated again into the story's estimate.
Steps to reproduce:
Seems pretty well broke to me. I've read in the bug description that this is not likely to be fixed, but this behavior in portfolio is clearly dangerous. Anyone know how to vote for this bug or report the above reproduce steps as a new, special case bug?
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot