You may want the names of your custom statuses to map to the statuses used in other third-party tools (like your bug tracking system). Or you can delete the example statuses and create new ones by clicking Add status. You can edit the workflow's example statuses to reflect your processes. There are two ways to add custom statuses. Workspace owners can change the default workflows if they need to. Aha! Roadmaps administrators can use this setting to drive consistency across workspaces of the same type. Once set, the workflows you select will be the default workflows the next time someone creates a workspace in that type. You can create separate feature / activity workflows for each record type, or use one workflow for all three. Note: Requirements and epics both use feature / activity workflows. You can set a default workflow, by workspace type and record type, by clicking Set defaults.įrom the modal, select the appropriate workspace type tab, then select the workflows you want to be the default for each record type. This ensures that records can be promoted and change in status as expected. If you are using a fixed workflow for ideas, check that the first status in your workflow has a status transition configured to the first status in your In Progress status category. When selected, only administrators with customization permissions will be allowed to edit or delete approval to-dos created by the workflow. If you choose to create a fixed workflow, you will also see the option to Restrict approval changes. They are best suited for workflows that need to be consistent, like a product development initiative that needs regulatory and financial approval before implementation can begin. They are best suited for workflows that do not follow the same steps in the same order every time - drafting a go-to-market blog post for a content marketing team, for example, with a variable number of reviews depending on the post's content.įixed workflows do not allow users to skip workflow steps and support approval gates. Next, select whether your workflow will be flexible or fixed.įlexible workflows allow users to skip steps in the workflow and do not support approval gates. Update the Name of the workflow and add an optional Description. You can customize your workflow once you have created it. If you want to use one pre-built for a particular workspace type, select it from the list of example workflows, then click Create workflow to create your workflow. If you want to create a custom workflow from scratch, select Simple example. You can create workflows for the following record types:įeatures / Activities Note: This also applies to epics, and to requirements. When you click the Add workflow button, you can select which type of record workflow you wish to customize. Use the Workflow type dropdown to filter the list of existing workflows. To add a custom workflow, navigate to Settings ⚙️ Account Statuses and workflows.Ĭlick the Add workflow button to create a new workflow.Ĭlick the Set defaults button to set default workflows. Use advanced custom layouts (Enterprise+) They can also clone workflows to create a copy for themselves or edit existing workflows to make changes.Ĭlick any of the following links to skip ahead: But any user with workspace owner permissions can apply created workflows to their workspace. You will need to be an administrator with customization permissions to create a custom workflow at the account level. You can also customize your team's record layouts, types, and statuses. You can customize your team's workflow by workspace so that Aha! Roadmaps mirrors however your team works best. An Aha! Roadmaps workflow is the set of statuses and transitions that a record such as an initiative, feature, or idea may move through during its lifecycle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |