Action types describe what a card represents, such as a task, a risk, or a decision. Use them to keep different kinds of project information organized and show custom fields relevant to each kind of card.
Choose the right type
Use these examples as a starting point:
Action: Work to complete, such as preparing a launch checklist.
Risk: Something that might affect delivery, such as a possible supplier delay.
Issue: A problem already affecting work, such as a missed delivery.
Assumption: Something your plan relies on that still needs confirmation.
Dependency: Something the project relies on, such as another team providing final assets.
Decision: A choice to make or record, such as selecting a launch date.
Feature request: A proposed addition or improvement.
Bug report: A report of something not working as expected.
Available choices depend on your view. Standard work uses Action. The Risks and Issues tracker offers Risk, Issue, Assumption, Dependency, Decision, Feature request, and Bug report.
View or change a type
Open the Risks and Issues app or a project’s Risks/Issues tab.
Use List or Table view and show the Type column.
Select the item’s Type cell, then choose an available type. You need permission to edit the item.
For example, change a Risk to an Issue when the potential problem becomes a current problem.
See Creating a Risks and Issues Tracker for setup steps.
Limit custom fields to specific types
Use action-type restrictions when a field is relevant only to certain cards. For example, show a “Mitigation plan” field for Risks or a “Steps to reproduce” field for Bug reports.
Open your profile menu → Settings → Workspace settings → Custom fields.
Create an Action field, or open an existing action field’s ⋯ menu and choose Edit.
Expand Advanced settings.
Under Limit to specific action types, select the types that should use the field.
Select Save. Make sure the field is also added to the projects where you want to use it.
Leave the type selection empty to apply no action-type restriction. Select Action explicitly if the field should apply only to standard actions.
This setting is available for action fields. It is separate from Conditional visibility, which uses other custom field values to control whether a field appears. See Custom Fields for details.