Getting Tasks into Changelogic

What is a task?

Every single request, requirement, problem, idea and bug coming from clients, analysts or testers is separate task on Changelogic. By definition, a task is a description of why and what you need to accomplish, while a change is the implementation of a task.
The life cycle of a task consists of Approval, Implementation and Verification.

One can enter tasks from two forms: either the short form or the long form.
Or you can let your clients enter tasks through your application.

Short form

The short form is meant to get your idea written down as fast as you can, it's designed to have minimum of required fields and those required, come with default values, except the Description.
You can access short form from “Tasks” menu.

All tasks entered from short form will enter the approval phase.

Here is an example of the short form:

Long form

Although entering tasks using the long form is a bit slower, the long form is a fast way to get the task to implementation – when entering task from this form, you already have to know what you want. Long form is meant for testers, analysts, developers and other stakesholders who are able to define proper requirements and have the authority to do so. Users having only client role in a project cannot use the long form for entering tasks.

Tasks entered from long form will go directly to implementation phase. Since the approval phase is skipped, there are many required fields. For bugs you should describe steps to reproduce, current behaviour and desired behaviour.

Here is an example of the long form: