![]() ![]() If all requirements have a status in the category of Done, then the feature status will change to Done. If any requirement has a status in the category of In progress, then the feature status will change to In Progress. ![]() ![]() The status changes of a feature's requirements affect the parent feature: If you do not have a status category of Shipped in your release workflow, shipping the release will revert the release to the first status in the category Not started. When a release is shipped, all features with statuses not in the categories Done, Shipped, or Will not do will be moved to another release.Īny features with statuses in the category Done will be changed to Shipped. Releases' statuses affect feature statuses: If the status does not match one of the category options, leave it blank. For example, Design and Development statuses might both be part of the In progress status category. You can have multiple custom statuses that have the same status category. When you add a new status or edit an existing status, you will be able to choose the status category that best matches. Status categories in Aha! Develop help you automate certain displays and actions. 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. Team owners can change the default workflows if they need to. Once set, the workflows you select will be the default workflows the next time someone creates a team. Note: Requirements and epics both use feature workflows. From the modal, select the workflows you want to be the default for each record type. You can set a default workflow by clicking Set defaults. When selected, only administrators with customization permissions will be allowed to edit or delete approval to-dos created by the workflow. Note: If you choose to create a fixed workflow, you will also see the option to Restrict approval changes. The majority of Aha! Develop users should use Flexible workflows. While they are an option in Aha! Develop, Fixed workflows are not well suited to most teams' workflows. They are best suited for workflows that do not follow the same steps in the same order every time.į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. #Bugzilla workflow customization updateUpdate 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, select an example workflow, 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 Note: This also applies to epics and 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. You can also customize your team's record layouts, types, and statuses.Ĭlick any of the following links to skip ahead:Īdministrator with customizations permissions You can customize your team's workflow by team so that Aha! Develop mirrors however your team works best. An Aha! Develop workflow is the set of statuses and transitions that a record such as an epic, feature, or requirement may move through during its lifecycle. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |