Data Missing Gantt Chart

Hi have just installed the gantt plugin and all the effort is at 0 days and in resource planning nobody's name appears?

2 answers

The prerequisite for displaying an issue on a Gantt-Chart is as follows:

  • having configured the main/global Gantt settings (admin mode, plugins, Gantt-Chart, config)
  • enabled Gantt-Chart for the related project XYZ (admin mode, projects, XYZ, Gantt section or left tab "Gantt-Chart")
  • having set planned start date and planned end date (both customfields are added automatically but are not assigned to any screen)
Both assigned planning dates are global and cannot be differently set per project. By default, they are named "planned start date" and "planned end date". If you want to use different names (within JIRA, no translation of customfields is possible / i18n), please create two new customfields of type "date" or "date/time" and name them within your own language as you need. Than, you have to assign them to start and end date within the global configuration, so that my plugin knows, where to find the correct start and end values.
Per project, you can set project-individual settings. These are not shared between the projects, e.g. you can specify the default time period. The time period can be specified as relative dates (like "-4w" to "12w": starting four weeks in the past til twelve weeks into the future) or as absolute dates (like "2012-06-01" until "2012-06-30"). I recommend the usage of relative dates as this will shift automatically according to the current date.
If you are using Greenhopper and have created JIRA versions having set start and end date, such a version will be displayed on the Gantt-Chart like normal issues to allow interactive linking (see below). They are displayed by using Greenhopper's version hierarchy appended at the end of the list of issues. If you do not want to show them, please disable project-specific setting "show empty versions/sprints". If you want to group issues below their assigned versions, please enable option "show versions/sprints".
Single Project views:
"Gantt-Chart" and "Resource Planning" are just different views on the same search result of issues, sharing the project-specific settings. If no issue has been found, no assignee will be displayed on the resource view either. Please check your time period: all issues fitting into this time period will be selected. Having a lot of issues, this feature helps to reduce the amount of displayed issues due to performance. Additionally, you can use stored filters as selectable right of the time period (if a filter's result contains issues not belonging to the current project, they are ignored on this project view).
Multi-Project views:
If you want to display a Gantt-Chart containing multiple projects, please add a "Gantt-Gadget" to your dashboard. Within its configuration, you can select projects or a JQL filter you have defined and stored before. If you have linked issues belonging to different projects using the defined Gantt-Dependency, this inter-project dependency will be displayed as well. Using interactive issue linking direct on the Gantt-Chart makes your life easier: click on the right bubble, shown when your mouse is over the Gantt bar, to start linking. Then, click on a left bubble of the target issue to finish linking. Keeping the mouse over a bubble will display a short hint after a short time (tooltip). Pre-requisite for this feature: assigned Gantt-Dependency within the global config.
Enhanced Issue Linking:
Using my Gantt-Chart add-on, you can link issues with versions and vica versa as well as versions to versions.
Pre-requisite: a version must have defined an own start date and end date (needs Greenhopper to do this). Purpose: if you have an individual test project, e.g. for integration testing, and created a test-task to validate correct interface behaviour between System A and System B. So, you link the related system versions to this task issue to define the dependency. This feature can be used for release management aspects as well.
First steps to check:
Please put both planning customfields and put them on your default screen (you have to do this in admin mode), if not already done. Then open an issue you want to see on the Gantt-Chart and watch both planning dates. They must be set to suitable dates. If not, please enter them manually and remember both values. Switching back to the Gantt-Chart view, ensure that at least one of the planning dates fit into the time period of the Gantt-Chart: you should see this issue, now!
Automatisation:
Instead of maintaining issues's planning dates manually, you need to set the original estimation (this is a human's job and cannot be automated). Having enabled the Gantt-Listener (global config), the planned start date will be set to today (creation date) and the planned end date will be calculated as start date + original estimation * velocity (please read its explanation on the global config tab "listener") taking non-working days into account. Having set a due date and original estimation, the planned end date will be set to the due date and the planned start date will be calculated like described before. If you are using Greenhopper and have enabled it for this project, the planned start/end date will be set to its sprint start/end date, if the related version/sprint is assigned and the sprint has defined start/end dates at creation time. Currently, my plugin is compatible with Greenhopper up to v.4.9.x - support for 5.x will come soon.

Handling already existing issues:
Switch to admin mode, select your project and open left tab "Gantt-Chart". On that panel, you will find a button "generate planning dates for issues having no start/end date" to do the job for you. If you have issues without any estimations of effort, it is not possible to plan them. For those, you can enter a default estimation.
I hope, this short description helps. If you have any further question, please do not hesitate to contact me.
Regards,
Frank

Additional feature, new in v2.0.0: a new customfield type "Gantt-Bar"

If you want more flexibility, you can create an additional customfield of new type "Gantt-Bar" (do not assign it to any screen as this will not output anything, currently). Then, you can use JIRA's issue navigator to select and sort the issues like you want. Afterwards, please configure the displayed columns, modify them and add the new customfield of type "Gantt-Bar". Having done this, you will see a Gantt-Chart integrated into JIRA's issue navigator. Afterwards, you can save this a filter and re-use it, whenever you need it.

I have optimized this to maximum performance. It is much faster than the standard Gantt-Chart. Step-by-step, I will migrate the algorithmns to this new approach.

If you enable the experimental/lab-mode, you will be able to use the Gantt-Chart-column with ALM's Structure add-on. But be aware: this is not for production usage, just as very early feature presentation for EAP-users (early access program).

You can find a short youTube-Video of the new feature at http://youtu.be/2iYNGOhseco.

Kind regards,
Frank

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Bridget Sauer
Published Thursday in Marketplace Apps

Calling all developers––You're invited to Atlas Camp 2018

 Atlas Camp   is our developer event which will take place in Barcelona, Spain  from the 6th -7th of   September . This is a great opportunity to meet other developers and get n...

77 views 0 5
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