Generate planning dates / time estimation

With the Gantt-Chart by Frank Polscheit it should work to generate planning dates / time estimation in an automatic way. But for me it doesn't work. Are we doing it wrong or is someone else also experiencing problems?

3 answers

1 accepted

0 votes
Accepted answer

Hopefully, now it seems to be working as expected, i.e.:

  1. Auto-correction, re-scheduling as well as copying of planning dates into corresponding baseline fields in case of first work logging
  2. Calculation of the duration of an issue in working days as (sum of logged work + remaining estimated effort) * 1/velocity*100

Now the calculation and re-scheduling seems to be working. But of course, without values Gantt-Chart can not calculate the planned and end date, so original time estimation is needed.

The Default velocity used for calculating a minimum duration: 100.0%

I'm having some issues getting anything meaningful to display, but it could be that I have incomplete data in our sandbox environment where we are testing this gadget.

The following seems to be required fields on Epics: Planned Start, Planned End, Original Estimate

The following seems to be required fields on Stories: Planned Start, Planned End, Story Points, Story Points Expended, Epic Link

Also... it seems that the Project must also have a non-zero velocity. True?

If all of this is true then we will not be able to use this gadget because we don't give stories Planned Starts or Planned End since that is not an Agile approach.

Ideally I would like for the Epics to have Planned Start, Planned End and show progress based on the sum of all storypoints and the sum of all Storypoints Expended. Is that possible?

So to be clear: Planned Start, Planned End and Original Estimate are all needed on the Epic, true?

But will the Epic bar be drawn if the attached story points don't have Planned Start and Planned End? but only storypoints and storypoints expended?

In the Gantt-Chart Global Configurations for the progress the JIRA time tracking can be used (as we do, hence we need the time estimation), or story points can be used.

Acc. to the description:

Issue Rescheduling
Re-scheduling as shifting planned start/end dates, keeping the duration in working days, for dependent issues as well as sub-issues will be performed, if:

  • one of the recalculations/events are triggered,
  • the feature 're-scheduling' has been enabled for their corresponding project (see 'Admin' panel on 'config' screen on the 'Gantt-Chart' project tab panel or within the project specific Gant settings),
  • the individual issue's Gantt option custom field (checkbox) has not been set to manual re-scheduling,
  • the dependent issue (issue linkage) or sub-issue has not already been started (no work logging).

Doing the first/initial work logging for an issue, the planning dates will be copied into their related baseline dates.
Issue dependency must be done by linking the related issues using the Gantt-Dependency type as configured on the Gantt-Admin-Panel (main JIRA-Administration screen). You have to configure the dependency types and create dependencies between issues using the JIRA standard link feature or interactive linking on a Gantt-Chart.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,717 views 3 11
Read article

Atlassian User Groups

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!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you