This section allows you to define workspace-wide options
for Issue behavior under specific circumstances, e.g., subtask creation
and closure, linking and moving issues. The
options are:
Copy/Move Issues Into This Workspace—Define the workspaces from which issues can be copied/moved into the current workspace.
All Workspaces—Issues can be copied/moved from any other workspace into the current workspace.
Selected Workspaces—If this radio button is selected, additional fields are displayed. Click a workspace in the Workspaces list and use the arrows to move the workspace into the Allowed list. To remove a field from the Allowed list, click the workspace and use an arrow button to move it into the Workspaces list. When an agent tries to copy/move an issue into the current workspace, the agent will only be able to copy/move issues from the Allowed list of workspaces into the current workspace.
Dynamic
Issue Linking—Select
which actions should be performed on Issues in this workspace when they
are being automatically updated as a result of a dynamically linked Issue
having been updated. The
options available are:
Update
Title—Checked
by default
Update
Status—Checked
by default
Update
Description—Checked
by default
Update
Priority—Checked
by default
Update
Issue Information Fields—Checked
by default
Update
Contact Information Fields in Issue—Checked
by default
Copy
New Attachments
Update
Contact in Address Book
Add
Contact to Address Book if New
Note
In the case of Issues dynamically linked across different
workspaces, statuses, priorities, fields, etc. that are not present in this
workspace do not carry over to the Issue in this workspace. Dynamically
linked Issues are not updated at all when a Customer performs an edit.
Also, note that, when using Issue Workflow rules, dynamically linked Issues in the receiving Workspace are updated even if the agent’s role would not normally allow that agent to update those fields if the Issue Workflow allows the update. In the case of customers, however, dynamically linked Issues are not normally updated, regardless of the customer’s role properties in the receiving Workspace.
Status
for Moved Issues—Select
the status for the source Issue when moving an Issue from the current
Workspace to another Workspace. The
default is Closed.
Subtask
Closure Process—Upon
the closure of the last non-closed subtask, FootPrints
can either automatically close the Master Issue or can either automatically close the Master Issue and send an email to the
assignees of the Master Issue informing them that all subtasks have been closed or send an email to the
assignees of the Master Issue informing them that all subtasks have been
closed without changing the Master Issue status. The
default is to automatically change the status to Closed.
Subtask Sequencing—This feature sets default Status names for the sequencing of Master Issues. An inactive Status has been built into FootPrints for Subtasks that are not due to be performed in the sequencing queue. This can be renamed by typing in the Name of Inactive Subtask Status field. By default, when a Subtask becomes active in the sequence, its Status is set to Open, but you can select a different Status upon activation from the Status Upon Activation of Subtask field. By default, when a Subtask is completed, its Status is set to Closed, but you can select a different Status upon completion from the Status Upon Completion of Subtask field.
Subtask
Automatic Status Change—Upon
changing the status of a Master Issue to one of the statuses selected
below, FootPrints can automatically
change the statuses of each subtask to that of the Master Issue.
Copy Subtasks Into This Workspace—When
performing a cross-workspace copy of a Master Issue, FootPrints can either
copy or not copy the subtasks as well.
Template Subtask Field Inheritance—Select which fields will inherit their value from the Master Issue when a Subtask gets created from a Subtask Template. Manually created Subtasks always inherit all fields. If there is a value for the Subtask field in a Subtask Template and the field is set on this page to inherit its value from the Master Issue, the field will take the value from the Master Issue and not the Subtask Template. For details on Subtask Templates, refer to Create Subtask Templates.
When you have selected the necessary Issue workflow options,
type in your password and click Save.