Use workflows to define the life cycle of your issues.
The behavior of any task in the system is defined through its workflow. A workflow allows you to set the rules for changing task states, and contains a set of priorities, states message types, transitions, and custom fields.
A priority is used to specify a suggested resolution order for a task. You can specify priorities for each workflow.
A state is the position in a workflow where a given task currently resides. While a task is in a certain state, it corresponds to a handler, who is the user responsible for this stage in the process of working with this task. This handler user must do his work before changing the state and assigning another handler to it.
Specify the Start state among the created task states. When a task is created, the system will automatically set its state to the specified start state.
Then specify Final task states. Once a task reaches the specified final state, the system will automatically update the task Close Date. You can specify several final states or none.
To change a task state, the user should add a message. One or several similar transitions can be grouped into each message type. A transition is a unidirectional link between two workflow states. Each message can be configured with permissions such that, for example, only a manager can perform the close message on an item.
You may want to create some properties such as version, release, platform, etc. These custom fields will only be available for the tasks associated with the specific workflow.