Implementing Tasks

• Changelogic
• Getting Started
• Implementation

Why create relations between tasks and changes?
Relations between tasks and changes enable Changelogic to tell testers, customers and other stakeholders in which versions and environments should they expect given tasks to be implemented.
See how you can turn it in your favor from version differences.

While we have no particular suggestions how you should complete the task given to you, there are some things you might want to know about how the tasks and changes affect each other when there is a relation between them.

When you are starting to implement a task, you are expected to add the implementable task to your change on the details page of the change. If you don't have a change yet, you may click button “Save & create change” on the detail form of the task to create one.

Changelogic will try to guess and adjust the state of a task whenever an implementing change is added, removed, started/ended development of, integrated or abandoned. The rules of guessing are as follows:

In some rare occasions, these rules may give false results. For example, when you are removing an implementing change after finishing its development to indicate that the task was not implemented in the change at all, the task will become “awaiting verification”. This is not a bug, though – in another situation where implementation of the task is not related to the change, such behaviour is absolutely correct. Verifying the task will reveal that it has not been implemented and send it back to state “awaiting implementation”.