Workload calculation based on version date

If you use the version date to calculate the workload (this is optional and can be configured in the General Options section of Workload Admin), this feature lets you use this date as the due date for the issues that are included within this version.

This can be used to calculate the workload for issues that have no due date and that are included within a version. Workload will calculate the workload using the version’s due date as the due date for all of its issues.

The two modes of operation are explained below:

Without version date (box not checked)

• • Each issue’s due date is taken from the issue itself (Due date or custom field selected as the due date).
  • If an issue’s due date is after the current date, this will be shown in the workload (even if it has no time remaining); it is before the current date, it will be shown in the prior issues indicator (only if it has time remaining).

Example:

There are four issues with different due dates and different times remaining

Assume the current date is 27 September

• • The workload will show the two issues with a due date after the current date (one of which has no time remaining)

• • The prior issues indicator will show one issue, the one with a due date before the current date and with time remaining

• • One issue will not be shown either in the workload or in the indicator, as it has a due date before the current date and has no time remaining.

With version date (box is checked)

• • Those issues with a Release version are not taken into account even if these issues have time remaining and their own due dates. Only UnRelease versions are considered. If an issue exists in several versions, only the UnRelease versions will be considered.
  • Once only issues with UnRelease versions (or issues with no version) exist, the due date is obtained as follows:
    • If an issue has its own due date, that will be its due date.
    • If an issue does not have its own due date, it will assume the version’s due date. If an issue has several versions (UnRelease), the due date will be that of the lowest version.
    • If an issue is not in any version, the due date is taken from the issue itself. If it has no due date, it will not be shown.

Example:

In this example we have ten issues with different due dates and different times remaining associated with different versions:

We have the following versions (version 1 is in Release):

Assume the current date is 27 September

• The workload will show four issues as follows:
  • PROK-7: Issue in an UnRelease version, with a version date before the current date but with a due date after the current date. The due date is its own due date.
  • PROK-10: Issue in an UnRelease version, with a version date after the current date (shown even though it has no time remaining). Since it has no due date, its due date is that of the version.
  • PROK-11: Issue in an UnRelease version, with a version date after the current date. Since it has no due date, its due date is that of the version.
  • PROK-13: PROK-13: Issue in an UnRelease version, with a version date before the current date and a due date after the current date. The due date is its own due date.

• The prior issues indicator will show The one/three issue/issues, as explained below:
  • PROK-6: Issue in an UnRelease version, with a version date before the current date and with time remaining.
  • PROK-8: Issue in an UnRelease version, with a version date before the current date and a due date before the current date.
  • PROK-12: Issue in an UnRelease version, with a version date after the current date but with a due date before the current date.

• Three issues will not be shown either in the workload or in the indicator:
  
  • PROK-4:Issue in a Release version.
  • PROK-5: Issue in an UnRelease version with a version date before the current date and with no time remaining.
  • PROK-9: Issue in a Release version.