Avo Feature Requests

On the "View changes" screen for branches, it would be very helpful to be able to "mark as resolved" (collapse) comments. Currently it seems like all that can be done to clean up the view is to delete them entirely.

To make the translation of the tracking plan changes into code changes more precise and intuative, it would be helpful to be able to tailor the pseudocode snippets to the implementation methods teams are using. For example if the web source is implemented with Google Tag manager, then the pseudocode would be on the GTM format, using the datalayer.push() method.

Make it easier to add and drop users in Avo.

We need a way to push a standalone event to become a variant of another existing event. We are discovering that designed events from different sources and teams are trying to get at the same analytics event, but have done it slightly differently as different events, instead of each as a variant of one 'source-agnostic' event. As we start to merge the events from disparate teams/sources into the same space, we will need to make them all variants of the more 'superordinate' new event, but we don't want to have to reconstruct the entire event in its new variant space by hand with all its properties, allow lists, triggers, images, etc as a variant for each one. For example, Source A created 'success-import-media' with its own set of properties and descriptions. Source B comes along and needs to use that event name with its own specifications. We want to: 1) Create a new superordinate event for 'start-import-media' 2) Take the original Source A specific event and make it a variant of the new 'start-import-media' event as 'start-import-media-source-a'. 3) Then we can create a new variant for Source B under the new superordinate event called 'start-import-media-source-b'. As a bonus, we'd like the flipside: to be able to pull an event variant out of an event as its own stand along event with a new name. This is more niche because we designed a bunch of event variants, but out bespoke validator won't pass them. So we need to pull them out as temporarily named standalone events to start developing them in the app and checking data before we fix the validator.

Being able to annotate for a specific event what the property description is more specifically would be helpful. For example: Property: "id" Global description: "contains immutable non-localized strings identifying the object" Local description for "Item Added": "the matchname of the item added"

Be able to add/remove property bundles on event variants

When Snowplow is used as destination, the event needs to point to the Snowplow schema. This can best be done with a pinned property. It would be nice to see in the AVO interface when there is something wrong with this property, or if it is not pinned or pinned to an inconsistant value (i.e. when you duplicate an event the schema property is still pinned to the source event) Now we get feedback from the devs that there is something wrong with the schema; would be great if there is a check on this schema property when building a branch or merging it to main

It would be really useful for admins to know if there have been any failures in publishing integrations. Whether by email or slack. Currently, if there is a failure with a publishing integration, we are only alerted if we check the Publishing page, or if an end user sees something.

Some times the scope of a branch changes over the course of implementation; for sanity's sake, I'd like the ability to be able to rename a branch to better represent the scope

I currently have no way to change the name of an event variant, the only way to do it is to archive the whole variant and start over