Issue TypeEvery Issue in AWorkload system is always of certain Type. Type is mainly a purpose of an Issue.Issue Type defines two main things about an Issue:
Information fieldsAWorkload allows you to define what fields User will have to fill in order to log (create) an Issue. Each of those fields can be set as Optional or Mandatory. It is also defined for Issue Type what fields of information User will have to fill when switching an Issue from one State to another. We do not expect all the information to come in one piece. Certain fields need to appear only at certain stage of Issue progression. As a part of Issue Type definition in AWorkload system you can do that. Issue StatesSome Issue Types may have as little as two States - "Opened", "Closed". For some purpose it can be just enough. There are business processes which require much more complex treatment where certain Types of Issues have to pass a number of functional steps to reach the end. Definition of Issue Type allows setting of those steps and their flow. Issue Type defines what State is assigned to a new Issue of this Type at first. Then it defines what States are available to switch to from each of possible States within this Type. It is also setting which of those States must be treated as "End-State" when no more attention is required to this Issue, and it sets what States can be treated as "Actually working". By "Actually working" here I mean states which represent someone actually spending time on it, which is the opposite to "Waiting" for example. |