I am trying to demo a burndown chart using Jira Agile. I have set up stories and sprints but when I start sprint #1 and I take the stories to the done state, all the story points decrement is done on the current date.
Is there any way to simulate the stories are being "done" on a concrete future date... so the burndown chart looks more "typical"?
Referring to your issue, there is already a feature request being raised : https://jira.atlassian.com/browse/GHS-1187 which is related to Evidence Based Scheduling (EBS)
Please feel free to vote on it to increase its popularity and add yourself as watcher in order to receive any latest updates from the developer and feedback from other user that is facing the same issue.
Hi all, could anyone provide some more information about this issue beyond what Daryl said?
My request is to know if there is any workaround which allows me to control the date in which a closed issue (story, epic, etc.) is considered close. That happens when you want to correct mistakes on the flow of issues in the Kanban board, want to see the effects of a "what-if" simulation in the burndown chart, etc.
Any help is very welcome!
Can a new-to-agile team survive and thrive in a non-agile culture? If so, what advice would you give to those trying to be agile in a non-agile culture? What's the key(s) to success? Share your thoug...
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