It is an option that is at the very top of our configuration menu for a reason. It is one of the config menus as it allows you to limit the number of loaded issues, define recalculation methods used on Tasks displayed inGanttchar, set up Task link synchronization and more.
Configuring a Gantt
Gantt Configuration itself is divided into few key sections which are described and explained in each paragraph below.
Gantt task Start date and End date configuration
One of the most important configuration is which fields will be used by the Gantt module to display Jira issues as Gantt tasks. It impacts the behaviour of Gantt, Resources and Roadmap modules.
Issue Limiter - Max Number of Issues Loaded
The first field is the maximumnumberof issuesthatcan be loaded inGanttchart and Gantt's WBS at loading time. This is tremendously helpful if you experience performance issues. By limiting the number of issues loaded at once, the systemhaslessdatato work with and can run faster than ever. Obviously, issues outside of the limit are available to the user by pressing the 'Load More' button which appears in such a situation. Each click loads the number of issues specified in this field. For instance, if you define 100 issues as the limit and have 700 of them in total, it will take 7 clicks to load all of them.
App's Default / Required Custom Fields
When the app is installed, it automatically defines and setsupcontextforCustom Fields, which it will use. These customfieldsare:StartDate, End Date, Baseline start date and Baseline End Date. The only thing we need to make sure about is that an available Context is set to Global (all issues). It also should be predefined, though we want to be sure that each aspect of our Jira is set properly in order for the application to work as intended.
We can do this by visiting Jira Administration (cog icon) → Issues → (FIELDS) Custom fields.
Task Link Synchronization and App's Dedicated Issue Links
Same goes for Issue Linking. When using the Gantt chart, users can click on tiny markers in form of a circle on each side of every element (Task, Milestone, etc.) and drag it to another in order to create a Task Link (meaning dependency between tasks). This is asimpledependecy, such as "Task A starts after TaskB ends". Since two Tasks can be linked together, and each has 2 circles (one representing the start, the other representing its end date), there are four possible combinations:
|Gantt: End to End Link||has to be finished together with →||has to be finished together with|
|Gantt: End to Start Link||has to be done before →||has to be done after|
|Gantt: Start to End Link||earliest end isstartof →||start isearliestend of|
|Gantt: Start to Start Link||has to be started together with →||has to be started together with|
The above presents a clean Jira instance with only our application. If you have other apps, you may see additional entries in the drop-down menu.
If Task Link Synchronization values are missing, they might have been accidentally removed. To reset link values, please go to the Jira Administration Panel (cog icon) → Issues → (ISSUE FEATURES) Issue Linking setup and enter values as below. They will be recognized by the app so you can select them in Gantt Configuration.
Please keep in mind though, that our apps' Gantt Configuration only allows Jira Administrators to map SoftwarePlant's custom links and dedicated (pre-defined) Jira Issue Links. If by any chance you have created custom links which define dependencies between Issues in your Jira Projects, there will be no possibility to map them in the Gantt Configuration therefore, the Gantt chart will not display such custom dependencies. They will exist in Jira environment, yet the add-on won't recognize them as valid dependencies.
The ASAP mode checkbox determines whether all newly created links should have the ASAP mode checked by default. It is important to note here that this operation does not migrate existing links to ASAP mode.