Status change rules allow the Administrator to control the process by which the status of issues can be altered. To conform to your company’s workflow, ExtraView can create status change rules based on three different workflow formats:
- Default Format: All users must follow the same rules for all different product, projects, categories, modules etc.
- User Role Format: Different state change rules apply to different user roles within your company.
- Product Format: Certain products can be changed to statuses that are different from those that apply to other products.
Status change rules can be switched off altogether, with the behavior setting named ENFORCE_STATE_CHANGE_RULES.
In addition, if you are using business areas and / or projects, the status change rules can be set independently for each combination. This gives the flexibility of setting status change rules for any combination of Area, Project and User Role, or any combination of Area, Project and Product. Thus the status change rules allow diverse tracking systems to be set up within a single database, each with their own process and workflow.
An important concept with status change rules is inheritance. When you have defined a combination of business areas and projects together with user roles or products, inheritance allows you to define a workflow at any point in the hierarchy, and have all the subordinate points inherit the same workflow. This provides an economic way of defining workflow, without having to provide a workflow for each and every combination of business area, project, user role and / or project that you define.
Note:If you provide even a single entry in the workflow matrix at any level in the hierarchy, then this is used as the workflow for the entire level.