The content of this Space is not the latest version of WBS Gantt-Chart for Jira.
We have separate Space for each version of the product. If the version you are using differs from the one in this Space title, please find the correct one from the below page. https://rssupport.atlassian.net/wiki/spaces/WGC/overview


Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

On this page:




Viewing the plan and the baseline

These are shown on the Gantt bars in WBS Gantt-Chart. You can also check the plan start and end dates on the WBS display.

Issues

The plan and baseline dates set in the issue are displayed as Gantt bars. The upper bar is the plan and the lower bar is the baseline.
The difference between these two Gantt bars represents the difference between the current plan and the baseline.

Versions

A version is displayed as a Gantt bar based on its start date and release date. The release date is displayed as a milestone (rhombus shape).

Viewing task delays

Warning alerts are useful for telling you if an issue has started or completed as planned. If there is a colored “!” on the left-hand side of the WBS, that means there is information about the status of the issue.

WarningExplanation
Green3 days prior to the start date
YellowHas not started yet - planned start date has passed
RedHas not completed - planned end date has passed

Clicking a warning alert will show the corresponding Gantt bar.

Viewing the progress rate of issues (percent done)

You can see progress for projects and versions on the WBS display. The progress rate is calculated as:

The number of resolved issues (date resolved is set) / the number of all issues * 100

Issue progress rates can be checked via Gantt bars, as well as on the WBS display. If the right-hand edge of a Gantt progress bar is to the left of the vertical dashed line (current date line), that means the task is behind plan. If the right-hand edge is to the right of the date line, the task is ahead of the plan.

Viewing the hierarchy structure 

The WBS display hierarchical structure shows the parent-child relationship of existing issues.
If an issue is displayed in gray this indicates that it is not directly related to the version displayed in the upper hierarchy (hierarchy structure is prioritized for display).

Viewing issue dependencies 

You can check for issue dependencies by looking at the blue arrows displayed between the Gantt bars. If there is a blue arrow from a predecessor issue pointing towards a successor issue, this indicates that the successor issue depends on the predecessor issue.

Types of task links or dependencies

There are four types of task links as follows:

TypeDependency
Start-to-StartA successor task cannot start until its predecessor task starts.
Start-to-FinishA successor task cannot finish until its predecessor task starts.
Finish-to-StartA successor task cannot start until its predecessor task finishes.
Finish-to-FinishA successor task cannot finish until its predecessor task finishes.


Viewing the critical path

Enable Critical path in Tools on the toolbar. The critical path is highlighted, while other task bars and dependencies are shown in a pale color. The WBS display cannot be edited when the critical path is displayed. Issues which are not loaded are not included.


Way to make critical paths

Calculation of critical path
The critical path is calculated as follows.

  1. All issues with the latest planned end dates are identified.
  2. Where the issues identified in Step 1 have dependencies, the issues with the latest planned end dates are selected.
  3. Step 2 is repeated for all issues identified in Step 2. The calculation ends if the issues do not have any dependencies.


Viewing the resources plan

Check Resource view in View on the toolbar. The resources view is displayed on the WBS display and in Gantt chart format.

In the resources view you can display a list of assignees, as well resources bars showing time periods horizontally and % workload (units) vertically. A red line (called a 'limit line') indicates the maximum daily workload.

The resource bar is displayed in green if an assignee's workload units are below or in line with the limit line. If the workload units exceed the limit line, the resource bar will turn red. This indicates that the resources plan needs to be reviewed.

If you move your cursor onto the graph in the resources view, the issues to which the resources are allocated during that period, and their respective workloads, are displayed in a list.

Please note this version contains the following bugs.

  • Issues which do not have planned end dates set are not displayed in the resources view.
  • If there are consecutive resource bars with the same total workload, the resource view tooltip displays the issue list for the first period only.


Default Values of Units

Initial values of workload units depend on how the issues are created.

  • Issues created from projects or versions -> 100%
  • Issues created from issues or issue template -> same value as the original
  • Issues created in Jira -> 100%

Also, when updating from WBS Gantt-Chart for Jira 7.9.1, or earlier, existing issues will have 0% workload units.



If you have any questions please feel free to ask a member of the Ricksoft community!

  • No labels