I have a project that contains a total of 87 issues. Of these, only 20 have been assigned due dates and time estimates. All 20 of these are in the version "Beta". All of them have a due date of Sept 1, 2013, which is 15 weeks away.
When I try to show the Gantt chart, I ask for the period -4w to 15w. This says that it has found a total of 13 issues, and the Gantt chart displays 13 issues.
When I choose -4w to 16w, the Gantt chart says it has found 24 issues, and the chart actually displays only 7 issues. Why does it claim 24 issues when the project only has 20 scheduled issues? Why does it only show 7, when it showed 13 for a period that is a subset of this one?
When I choose 16w to 16w, the Gantt chart says it has found 5 issues, and the chart actually displays 5 issues.
When I choose 15w to 16w, the Gantt chart says it has found 17 issues, and the chart actually displays only 7 issues. One of the issues that showed up for the period 16w to 16w does not show up in the 15w to 16w search.
I can't make any sense of these results. They are not random, but they are completely unreliable. What is going on?
It turns out that if I specify a range of -4w to 52w then the Gantt chart says it has found 30 issues, which does not make sense, and it then hangs forever with the message "please wait while loading" while the little loading animation runs.
Error: TypeError: D[A].getStart(...) is null
Source File: http://example.com:8090/s/en_US-lcmsg2-418945332/852/12/1/_/download/superbatch/js/batch.js
an issue is displayed on a Gantt-Chart, if it has defined a planned start and end date and the related period is included within or intersects the time period being defined by from-to. Open your browsers console, you will see the corresponding JQL-statement to verify the result set within JIRA's Issue Navigator (search issues).
You can download my latest version pre-v2.3 from my server at:
Thank you, Frank. I have some progress to report:
1) I have downloaded and installed the latest version from your site. It no longer hangs up on "please wait while loading", which is good.
2) I have been unable to locate the embedded documentation. I'm willing to accept that I'm just blind, but can you please tell me where to find it?
3) I have an explanation for the strange time range behaviour I am seeing. It looks like a bug in the plugin:
None of my JIRA forms contains either Planned Start or Planned End, and they were not made visible when I installed the Gantt chart. I was able to figure out how to make them visible, but we've never used them for anything in the past, so they are mostly empty. They apparently were populated implicitly when I set the Due Date and Original Estimate fields. Some of my issues contained a Planned End but no Planned Start (I do not know how these occurred - we did not explicitly set them). The Gantt plugin is failing when it encounters issues that have no Planned Start.
I have tested this, and it is reproducible. Simply remove the Planned Start from any issue and attempt to chart the project. Only some of the issues will now be visible in the Gantt chart.
switching to admin mode and configuring my Gantt-Chart, you will find additional information on each tab panel embedded as well as by clicking on the link "Operational hints and inline documentation" on the result page after hitting "apply".
For your convenience, I have attached the most important info:
Automatic re-scheduling of planning dates: you must have enabled JIRA time-tracking!
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:
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.
In Scrum, velocity is how much product backlog effort a team can handle in one sprint. This can be estimated by viewing previous sprints, assuming the team composition and sprint duration are kept constant. It can also be established on a sprint-by-sprint basis, using commitment-based planning. Once established, velocity can be used to plan projects and forecast release and product completion dates.
How can velocity computations be meaningful when backlog item estimates are intentionally rough? The law of large numbers tends to average out the roughness of the estimates.
The value of velocity is a percentage with a default value of 100%. If your team's velocity is generally slow, respectively over-estimate themselves, please adjust the parameter below.
For example: enter '75' als velocity, if your team finished an amount of 75% of the issues they have estimated within a time period. Based on this velocity parameter, planned start dates will be calculated as planned end date minus original estimation (duration of estimated effort taking weekends into account) multiplied by the velocity factor to stretch the timeline. The velocity factor will be calculated internally as 100/velocity and is 1.333 in this example: 3 days effort needs 4 working days to be finished.
Again, thank you, Frank. I cannot find that documentation anywhere. What do you mean by switch to admin mode? Do you mean JIRA admin? When I do that I can administer the project, but I cannot view the Gantt chart. In the Gantt chart panel I have three tabs, "Project Configuration", "Project Calendar" and "Import Project". None of these pages contains a link for "Operational hints and inline documentation". Can you please be more explicit about where to find the documentation? I have spent a long time searching and I just don't see it.
Also, does this mean that my users cannot read the documentation without admin privileges? How do I give my users access to it? Do you have an on-line documentation page that they can see?
Regarding the missing issues in the chart, there are two bugs that I can see:
1) When the Gantt chart finds an issue with no Planned Start, it stops showing any issues after that, even valid issues. That is a bad bug because it silently stops showing valid issues with no indication whey.
2) The documentation says an issue needs both a Planned Start and End, but Gantt chart is processing issues without a Planned Start.
Gantt chart should
a) ignore the issue,
b) clearly indicate that it has found an issue that is not completely specified, or
c) add a default Planned Start.
Currently it aborts the chart, hiding valid issues, and produces no error or warning message. If one of my users makes a little mistake, his entire chart is corrupted without any indication why.
you need JIRA system admin privileges to configure my addon and access the inline docu, I have provided above.
Did you install the v2.3 I have published on Atlassian Marketplace or an older one?
Please open the browser's console and you will see the JQL-statement, used for issue retrieval.
If you do not provide any planning dates while creating an issue, today will be used a start date and the end date will be calculated using the original estimation * 1/velocity. If no estimation has been entered, the end date will be set to start date (duration of 1 day). Pre-requisite: you have enabled re-scheduling within the Gantt-Chart main configuration as JIRA system administrator maintaining your JIRA instance.
I have installed version gantt-2.3-JIRA5.2-JIRA6.0-UPM2.10.jar from the link that you provided above. I installed it over v2.3 from the Atlassian marketplace.
I have administration privileges and I can configure the addon. As I said above, when I look at the addon configuration in administrator mode, I see three tabs - "Project Configuration", "Project Calendar" and "Import Project". None of these pages contains a link for "Operational hints and inline documentation".
Please just tell me the specific things I must do to access the documentation. I have searched and searched and I just do not see it. Perhaps you think I am blind, but your documentation is very well hidden.
If people must have administrator privilege to access the documentation, how can I make the documentation available to my users?
Regarding the bugs: I was working with a project that already existed, so the start and end dates, due dates and estimates were all empty. Somehow, the end dates became set, but not the start dates. The Gantt chart plugin then could not show a chart, even for the issues that were valid. This is a serious bug because my users could do the same thing and then the chart will produce wrong and unpredictable results without warning.
All I am asking is that you handle the case of invalid dates in any manner except producing a partial or invalid chart. I would be perfectly happy if you simply put a warning on the screen saying "One or more issue has invalid dates. Cannot draw the chart." Please just don't silently fail half-way through drawing the chart with no error message.
as JIRA system admin please click on "Administration", then click on "Plugins" and choose menu item "Gantt-Chart" for my addon configuration as I have written above: there you will find the several tabs I and "Operational hints" on the result screen after hitting "apply".
Please install the latest version 2.3 I have published on the Marketplace.
I tried to reproduce your case, but it works fine in my test environment having set a larger project with 1000 issues, manually delete the planned end date of the third issue and the Gantt-Chart is displayed correctly containing all other 999 issues without #3, which I modified.
May be, it is possible for you to make a TeamViewer session on Monday, 27th of May as next Monday is a public holiday in my country?
Thanks, Frank. I have now found the operational hints and inline documentation. I would never have guessed to look there. Maybe you could put a "?" button on the Gantt chart somewhere.
The operational hints and inline documentation does not contain nearly as much information as what you posted above. Is your posting above from a larger document that we have access to?
Regarding the test case, please delete the "Planned Start", not the "Planned End". It fails for me with 100% reliability.
1. good point, I will think about better positioning
2. that information is splitted into multiple parts on the various tabs and the section "operational hints"
What version of Gantt-Chart and JIRA are you running currently?
Not using the offered TeamViewer session for support, you can enable debugging mode writing more detailed information into JIRAs logfile. Proceed as follows:
1. stop JIRA2. rename JIRA's logfile to e.g. "OLD-atlassian-jira.log"3. edit file "log4j.properties" and append the following 2 lineslog4j.logger.de.polscheit = DEBUG, console, fileloglog4j.additivity.de.polscheit = false4. restart JIRA (a new empty logfile will be created: that helps to focus on the problem and limit the amount of data)5. login and repeat your actions in order to reproduce your local problems6. send me your JIRA logfile for further analysis
I'm using JIRA version v5.2.9#852-sha1:71473fa
I'm using Gantt-Chart version
gantt-2.3-JIRA5.2-JIRA6.0-UPM2.10.jar from the link you posted earlier in this thread.
Were you able to reproduce the problem by removing the "Planned Start" date from an issue?
Sorry I can't offer you a TeamViewer connection to a machine here. I realize that would speed the process, but I think you should be able to easily reproduce the problem by deleting planned start from an issue.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
One of the newest products in the Microsoft family - Microsoft Teams, is a chat-based hub for teamwork that integrates all the people, content, and tools your team needs to be more engaged and ...
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