RELATED IDEAS
Allow custom statuses to inherit from product line
The update to allow customizing the default status is great.
However, it doesn't solve the problem where we have multiple business units in a single account and each business unit has their own distinct workflow for their portfolio of products.
Setting the default allows one business unit to be happy - but at the expense of the others not being able to realize the same benefit.
What we need is for statuses to be inherited similar to custom fields where a custom status set at a product line is automatically applied to all newly created child products.
-
ADMIN RESPONSEMay 18, 2022
Create custom workspace templates
Standardize the way you set up new workspaces so teams follow the same approach. Create a template with predefined workflow statuses, custom fields, automations, and more. This update is available for customers on our Enterprise+ plan.
Checkout the blog post for more details.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +8
10
MERGED
Option to apply workflows and custom forms to all or multiple products
When setting up things like idea workflows or custom forms for idea submission you currently have to apply these changes to each product individually. It would be good to have the option to apply the changes to the current product, multiple produc...
0
Shipped
2
MERGED
Workspaces should be able to inherit epic/feature workflows from parent lines
Workspaces should be able to inherit epic/feature workflows from parent lines. Currently it's only possible to set the workflow for each artifact type at a workspace level. It should be possible to set the required workflow at a workspace line lev...
1
Shipped
I currently have 61 work spaces under a single integration template. It would be great if I could apply a workspace template in bulk when changes are being applied to any setting. Going through and updating the work spaces is tedious and time consuming. This functionality is ESSENTIAL to anyone trying to administer anything of this size. We cannot make any changes without them being painful and the system wasn't set up correctly from the very beginning so I'm feeling so overwhelmed and buried in the most basic of changes to ensure that maintenance moving forward is easier so I can move out of this role. Please complete this SOONER THAN LATER!!!!
Its a lot of manual work to change the workflow at individual workspace level. There should be an option to inherit the master workflow in order for consistent reporting
Agreed. The integrations should also not loose the status mapping when switching between workflows if the statuses in that workflow have the same names.
essential functionality.
Agree on this. It's such an oversight that I can't believe this was released without consideration. The Product line workflow should be able to be the same as a product workflow. It's insane that this is not the case.
To reiterate what the 2 people stated before me, we really need this ability within the tool. Within our organization we have more than 800 products and product lines. Applying the workflow individually means hours of tedious manual updating. It is imperative to be able to apply to many or all of our organization hierarchy quickly.
Fully agree with previous comment, I would like to define the workflows at a Product Line level and ensure all the products underneath can simply inherit from above instead of relying on a default workflow.
1) if I create a new workflow, I don't need to change each and every product manually
2) if I have different divisions working with different workflows they can all make sure all their products are using the same
If we decide to make a change to our feature workflow for handful of products, it is incredible annoying to have to select each and every product and change the workflow individually. If I could apply the workflow to multiple products at once, or set it at the product line level and have that inherited by all products beneath it, that would save me a ton of time.