Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Metrics for release Forecasting

I would like to see release/ Epics predictability based on three scenarios Standard, worst and best or something similar. Has anybody tried forecasting similar way 

2 answers

0 votes
Danut M _StonikByte_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Feb 15, 2023

Hi @Ashish Nagpal,

With our Great Gadgets app for Jira & Confluence you can generate burndown/burnup charts with forecast for Jira project and epics.


However, it only displays one scenario, based on average velocity. But it this is so important for you, we could consider adding the worst & best scenarios.

If you have questions, please don't hesitate to contact



0 votes
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 17, 2019

Hi Ashish,

I am not aware of any method or add-on that could provide an automated method to achieve a multi scenario approach or best to worst case timelines; but for a manual approach you can look into setting up Multiple scenario planning, and in each of the scenarios adjust the weighted items of the scheduling factors (i.e. rank, estimates, capacity, dependencies,  etc...) to get the varying level of comparison, best to worst on the plans layout, and after reviewing commit the one that looks to be the most achievable.

Using this approach as your primarily looking at the Release variable you could set up one scenario with a "As early as possible" start date and a "dynamic" release date and the second with the optimal fixed dates and the third with a conservative fixed dates to compare the three variable plans and see if there are any conflicts in the schedule on each scenario.

Also check out the documentation for "Scheduling behavior" that goes into more detail on how the item weighted items are calculated. 


Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events