Configure Workflow for Issues of Topic Page

This page displays information relating to configuring workflow for issues of an issue topic.

New issues

An issue topic identifies what an issue is about, and thus serves as a way to categorize issues.

The workflow configured for a topic determines what happens to an issue from the time it is created. To learn more about workflow, see Ketura Tour Step 8: Workflow.

The State transitions and State behaviour tabs on this page are used to configure workflow for this topic.

This tab shows the milestone to which new issues of this topic are added.

To change the milestone to which new issues of this topic are added:
  • Change the selected milestone in the drop-down list box, then click the Apply button.
To abandon changes before you have applied them:
  • Click the Reset button. The field will be restored to its previous value.

Description of form fields

Automatically add new issues to milestone A drop-drop list box showing the milestone to which new issues of this topic are added. For example, new issues for a given topic might be added to a milestone Review new issues to ensure that someone has the responsibility of reviewing every new issue.

Issue state transitions

Using issue state transitions, a particular workflow can be enforced by configuring the allowable transitions between states.

Information This form is much easier to use if your browser window is resized to be wide enough to show each table row on a single line.

Ketura makes it possible to define sophisticated workflows to guide issues from creation to completion. However, it’s possible to use Ketura productively without explicitly defining any workflow at all.

This tab is used to define issue state transitions, which describe the automated workflow for an issue topic. Workflow determines what happens to an issue when it is created, the states that it must subsequently pass through and the tasks that must be completed for each state.

For example, it might be possible to change a state from ‘New’ to ‘Awaiting Scheduling’ or possibly a ‘Rejected’ state, but not directly to any other. Then, from ‘Awaiting Scheduling’, the only allowed transition might be to state ‘Pending Resolution’. By specifying the allowable state transitions in this way, particular workflows can be enforced.

See Ketura Tour Step 8: Workflow for more information.

Depending on your permissions, you may be able to perform the actions below.

To allow transitions from one state to another:
  • Locate the initial states in the From State column of the table.
  • Check those states to which transition is allowed.
  • Click the Apply button.
To restrict transitions from one state to another:
  • Locate the initial states in the From State column of the table.
  • Uncheck those states to which transition is not allowed.
  • Click the Apply button.
To change the possible state types:
  • Follow the Manage State Types link found at the top left of this tab.

Description of table columns

From State The state from which the issue is moving.
Allow Transitions To States The states the issue is allowed to move to, indicated by checked checkboxes.
To abandon changes before you have applied them:
  • Click the Reset button. The checkboxes will be restored to their previous states.

State behaviour

This tab is used to define the tasks that must be completed for an issue to be resolved. An issue can automatically be populated with tasks from a task set when it enters a particular state. Each task in the task set can be assigned to a particular person by default, but can be reassigned if desired.

Marking existing tasks as complete when an issue enters a particular state

It is sometimes desirable to mark all existing tasks as complete when an issue enters a particular state. For example, if a Resolved state exists, it is likely that all tasks should be marked as complete when an issue enters this stage.

If a state has been defined as inactive, existing tasks will always be marked as complete. Inactive states can be identified by disabled checkboxes that are checked.

Depending on your permissions, you may be able to perform the actions below.

Prompting for comment when an issue enters a particular state

Prompting for a comment whenever an issue changes state can be useful in ensuring an issue’s history is kept up-to-date.

See Ketura Tour Step 8: Workflow for more information.

To mark existing tasks as complete when an issue enters particular states:
  • Check the Mark Existing Tasks As Complete checkboxes that correspond to the states.
  • Click the Apply button.
To prompt for a comment after an issue enters particular states:
  • Check the Prompt For Comment After Issue Enters State checkboxes that correspond to the states.
  • Click the Apply button.
To add tasks from a task set to an issue when it enters particular states:
  • Select the desired task sets from the Add Tasks From Task Set drop-down list boxes that correspond to the states.
  • Click the Apply button.
To abandon changes before you have applied them:
  • Click the Reset button. The fields will be restored to their previous states.
To change the possible state types:
  • Click the Manage State Types link that can be found on the top left of this tab.

Description of table columns

When Issue Enters State The state into which the issue is moving.
Mark Existing Tasks As Complete When checked, the existing tasks are marked as complete when the issue enters the state.
Prompt For Comment After Issue Enters State When checked, a prompt for a comment appears after an issue enters the state.
Add Tasks From Task Set A drop-down list box, set to <none> if no tasks sets should be added to the issue when it enters the state. Otherwise, the name of the task set added when the issue enters the state.