Cycles from DEV to QA – Average (Tasks)

The average number of cycles from Development to QA for tasks. A cycle represents the deployment of all the transports for a task into QA for testing. Each time there is a test failure another development cycle will be required to fix it. More than 1 cycle indicates a rework.

Parameters
CALC_METHOD=CYCLES
ROLETYPE=Q
TIME_TOLERANCE=1
FILTERTARGROLE=P

Documentation of operation and logic
Calculates the average number of cycles for tasks from Development to QA.
A cycle is a continuous interval of time during which the task is in Development in a given transport path.
The cycle ends when all the component transports for the task that were created before the given date and time are imported in a QA target system and no other transport is created within the time tolerance period.

Start time: Earliest of the transport creation, transport form creation or transport release for any component transport of the task (outside the TIME_TOLERANCE period (1 hour))
End time: Last import import into a QA target system (ROLETYPE = Q) for ALL of the component transports of the task
The start time of a new Development cycle will be considered only when the time set in TIME_TOLERANCE is exceeded (default is 1 hour)

Values are reported at the end of last cycle, only if the task is fully imported in FILTERTARGROLE (Production).

Note: When a task involves several characteristics (E.g. supplier) all characteristics get the full amount, but get an averaging weight based on the transports they contributed to the task.
So if a task has 5 cycles, with 2 transports from supplier A and 8 from B, both A and B will get a value of 5, but B’s value will count 20% of the task on which they worked alone, while for A it will count 80% of the task.