| Workflow allows you to define rules for field access and layout, based on issue criteria rather than the group settings that can be achieved in the field control menu. A workflow rule will enable you to catch flow states of issues and define possible future states or immediate actions based on the current state of an issue. Common examples include: control who can close an issue. only allow access to a field after a give state has been achieved. control the flow of an issue from state to state.Work flow rules are defined with a filter definition that is used to calculate state matches when working with system issues. If an issue is matched, a set of requirements and restrictions can be tested, actions can be executed, and new field sets can be defined for limiting flow or field access. The rules are arranged in a lookup order that is used when determining if an issue state matches any existing workflow rules. When a match occurs, that workflow rule is used to control what actions to take for an issue. Click here to see an example thatillustrates how workflow rules are summarized and organized. State Definition The state definition is a filter that is used to identify issues that will be affected by the current rule. Issues are checked against the definition to see if the current rule is relevant. Restrictions Restrictions are used to determine what individuals are allowed to move an issue to a given state. If a restricted user tries to move an issue to a state, they are returned an error message. Requirements A workflow rule can test that a given set of requirements exist, before allowing an issue to reach a given state. Requirements are defined as a filter, just like the actual workflow definition. If the requirement filter is not passed, the user is returned an error message Actions If the new state of an issue matches a given workflow definition and the requirements and restrictions are passed, then a set of actions can be performed on the issue state change. The Action Notify List is used to notify users of this state change.
The AutoChange field will change the value for a field to the indicated value Flow Control Flow Control limits the list options for the given state.
The example given says that for a bug in the [Ready to Release] state, the only selectable options that will show up will be the ones listed:"Closed", "Deferred", "Ready For Release", "Ready For Retest", "Rejected" You should include the one in the state definition, because it is the one that needs to be defaulted to. If it is not present, the first on in the list will be selected by default and may not be noticed. Alternatively, you could make it an always mandatory field, so that something is always chosen. Field Control The workflow field controls are used to control field attributes for the current state. This option expands the Field Controls menu in the Admin menu which is limited to group sets. The Mandatory setting forces users to enter data in a specific field. This option adds an exclamation image in front of a mandatory field so that it is obvious to the user. If the user does not edit the field, they are presented with an error message and must hit the back button. There are two classifications of the mandatory setting. The Yes option forces a user to submit data when a new bug is created. This is useful to ensure that users add enough information for a new issue and do not accidentally enter the default setting, or leave an important field blank. The Always option takes the functionality one step further, by ensuring that data is entered at every step.This is extremely useful for the AssignedTo field so that the correct person issent the notification on every update. Without this setting, an updater may forget to change the user name and the notification may never be sent. Field data can also be restricted using any of the following options:
The Read/Write (R/W) option is the default for all editable fields. Thisoption allows a field to be read and modified on any update.
The Read Only (RO) option restricts a group to reading privileges only.
The Hidden (H) option hides a field all screens.
The After Create (AC) option restricts reading priveleges after the issue is created. 
|
