|
|
AWorkload glossary
Following is a short description of terms commonly used in AWorkload service. You can click on a term for getting more detailed and illustrated explanation of the term.
|
Issue
|
Common term for a single task, order, enquiry, request etc. Something which can be started and finished as a single unit of work.
A single Issue always has the following attributes:
- Number - unique identification of it
- Definition - a simple text description or more complex structure of many data fields;
- Type
- Project which it is related to
- State
- Assignment
|
|
Issue Type
|
A single category of Issues which defines the content of a particular Issue and its progression from the moment it is created to the final state.
|
|
Issue State
|
Position of an Issue progress. It indicates what is happening with an Issue at the moment. Issue States are generically qualified as Working States, Ending States and other.
|
|
Issue Assignment
|
Relation between an Issue and Division which indicates who is currently responsible for an Issue.
|
|
Project
|
Subject of work. AWorkload uses this word for aggregation accounts of time expenses, grouping Issues by their subject, describing the structure of nested subjects etc.
|
|
Project Type
|
Category of Projects which defines the content of a particular Project, Issue Types allowed for it and some other rules.
|
|
Division
|
One element of organization hierarchy - Company, Department or Position. It can be occupied by a single User or can be vacant. It can have a single parent element which reflects the line of reporting in organization (a single boss).
|
|
User
|
A person who is registered as AWorkload user and logged on to any of AWorkload on-line services. User can be an occupant of any Divisions. Occupation of Division by an User establishes relation between that User and Projects, Issues and administrative privileges.
|
|
Copyright © Gnum Software Limited - 2011.