IssueWhen there is some attention required to some subject and that subject can be addressed as a solid distinct entity - that subject is an Issue. OverviewBase element of AWorkload system is an Issue. Unfortunately it is a bit too abstract term to be able to point a finger and say "This is what Issue is!". The good news however is that once your intuition absorbs this term it becomes an easiest thing to operate with. Issue is like word "thing" in some respect, but a bit more strictly defined in it's applicability. It depends on what you use it for. Whatever your business is defines what your Issues are. Here is a few more or less strictly defined descriptions of what Issue in any application might be. 
Every Issue in AWorkload system has the following set of attributes:
NumberIssue Number is unique numeric Id by which a single Issue is distinct from the others. Every Issue on your AWorkload Account is addressed by it's Number. Number of Issue is the part of Issue-related information always presented to you first. Search box in AWorkload system Web User Interface assumes that any numeric value entered in it is an Issue Number. As result it brings you details of an Issue corresponding to a Number you entered when you do so. DefinitionApart from the Number given to an Issue there is always some detailed information which describes the Issue. Content of that information depends on what Type of Issue we are talking about. For some Types of Issues just a text "Description" is enough. For some there is more details required. In either case there is always a piece of information standing behind any Issue Number. That information forms an Issue itself. AWorkload system is very flexible in terms of what details are required/allowed for logging an Issue of certain type.It is also worth a notice that bits of that information can be added as Issue is progressing, not necessarily at the very beginning. Issue TypeEvery Issue in AWorkload system is given a certain Type. Those can be for example - "Appointment", "Order", "Bug", "Enhancement" etc. In fact that is really up to you what Issue Types are suitable for your business. It is important to notice here that any Issue always has a single Issue Type associated with it. Rules applied by the system to an Issue depend on that Type and partially defined in it. Worth a notice that Type of an Issue can change if necessary. In order to enforce consistency AWorkload allows you to define what Issue Types are convertible from one to another in the definition of Project Type. ProjectIssue is always associated to a single Project. That relation allows AWorkload to calculate Project-related statistics and implement Project-related queries. Issue can be transferred from Project to another. StateEvery Issue has always one particular Issue State. It is indicating what is going with it. It is also has an affect on what can o can not be done with an Issue. As Issue progressing it is changing from one Issue State to another. There are rules of what Issue State can be followed by another Issue State and those rules are defined as part of Issue Type definition. In most generic terms State defines whether an Issue is
AssignmentEvery Issue is always assigned to someone. In AWorkload we assign Issues to Divisions which represent part of the business or particular Positions in it. Current Assignment defines certain rules applied to an Issue and allows AWorkload system to perform Division-based queries and statistics. Issue SourcesAWorkload allows a number of methods how an Issue can be logged (created):
|