will love it as well

We are coming back to this feature request regularly, we have the same use case as Kyle and Mark. Feature releases are done in phases, resulting in branches being split, which is now very manual (delete events from one branch, recreate them on another branch)

Ran into this again today with a branch that included both events which were released to production, and some which needed rework. We had to decide whether we wanted to merge changes that weren't in production yet, wait to merge the branch until everything was fixed, or remove the events which were being reworked and recreate the changes in a new branch. :(

I've read all the comments and use cases here and our use case is similar as well to this request "Clone a branch / branch out of a branch / merge a branch into branch".

We want to create the requirements for multiple upcoming projects at once as our timeline for creating the requirements is faster than the development time. We want to keep the branches smaller so it can be implemented simply but while waiting for implementation of the first branch, we're not able to use the requirements we already created in the first branch for the following branches which requires these implementations as well.

As a result, we either need to combine projects into one branch which increases the scope, or we need to re-create the overlapping properties/events/metrics in another branch one more time.

Yes, this is probably more specific to duplicating a branch. My use case is the same as Kyle's. We have teams which create a branch with multiple events, but might break up implementation across multiple releases. While creating smaller branches would solve for some of this, we'll always face situations where what we thought would be within a given release is deprioritized, more complicated than expected, etc. So this feature would help by allowing us to:

I think the name of this feature request doesn't quite capture what it's about. I think it would help if we make it more specific.

For example: "Clone a branch / branch out of a branch / merge a branch into branch"

Claire Armstrong, mark.hannah@th2.com, Ursula Ll, Giorgio, Davi, Kirill Yakovenko, Baldur and anyone else interested in this:

Would you agree with that reframing?

I'd love to clone a branch with an added optional step to flip off "Implement with Avo" for one source on original branch, and back on for new branch. Use case is I create a branch with includes multiple sources/platforms, but one team implements much faster than the other. Having to flip off checkboxes and add tags manually to 50+ events, merge, start a new branch, and re-check everything is very time consuming.

Another usecase for more flexible branch workflow:

A team has a branch with new events and don't manage to implement all of them before they want to ship the implemented events. Would be good to have a way to merge the implemented events and keep the unimplemented events on a branch.

Proposed workaround:

1/ remove the source off the events that weren't implemented - and add a tag to them

2/ merge the branch

3/ create a new branch

4/ add the source to the events again - using the tag to identify them