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
"Default Estimates" do not exist anymore in the improved interface :( This was a very useful feature. It helped me to judge roughly the overall scope quickly independent of timing . What feature replaces this and how?
@Alexander Dobry - In the new improved UI, it give you the ability to set what date fields that you want to use to your scheduling for your issues. In the old live-plan UI, the application uses the internal calculation for "Scheduled Start/Scheduled End" fields (in our case, it was associated with the issue's release association).
You can click on the clog wheel and select "Configure" option and go to the "Scheduling" section to see the setup
Hope this helps (assuming I understood your ask).
Best, Joseph Chung Yin
Jira Functional Lead, Global Infrastructure Apps Team
Thank you, unfortunately not :) I do not use dates / time to judge scope of work. If I have a lot of still unestimated stories , the former version allowed me under schedule to preset a default value for an "unestimated story" e.g. greyed "8" see pic above. With this I quickly get an rough rolled up value on Epic level across all stories. The new version does not provide this opportunity. Now I need to enter story points in each story to get the same result.
@Alexander Dobry - Here are some additional details on the New AR (improved UI) versus the old AR's (Live Plan UIT) on auto-scheduling of unestimated tasks comparison -
It seems the default story point for unestimated tasks configuration is no longer available in the new improved UI.
Here is another link on Scheduling for AR
Hope this helps.
I have the same question/problem. We use Kanban, and follow the best practice of creating issues that roughly the same size. It saves a huge amount of time so the developers can spend more time doing what they enjoy and are good at - developing - versus sitting in planning meetings trying to put together an estimate for every ticket.
This is a main tenant of Kanban - all tickets should be roughly the same, so flow (and planning) can be calculated based on the number of issues addressed. Thus a default estimate should be used for scheduling.
It is very disappointing that the "improved planning" doesn't allow defaults to be set. Is this feature coming to the system soon?