RELATED IDEAS
Support Team and Workspace automation rules with "same as" actions for any sprint
What is the challenge? |
Currently, automation rules with sprints only allow you to set actions that are based on the current sprint, not any sprint. You also cannot set "same as" action rules for related records. This means if you'd like requirements to move to sprints that their parent features move to, you need to move these manually |
|---|---|
What is the impact? |
Moving records between sprints requires manual effort |
Describe your idea |
Support automation rules that allows actions to be "same as" related records for any sprint, rather than just the current sprint. |
-
-
-
-
-
- +1
© 2025 Aha! Labs Inc.•All rights reserved
Hi, Could you give me an example of the rules that you want to set. Just imagine that it is all working and you can do what you need to can you write me the rules you would expect to see.
This is super important to maintain a sprint, ensuring it has the correct work in it, and keeping work together when the plan changes (which it often does!). Currently very manual and prone to items being missed which delays features being shipped to the user.