Avo Feature Requests

I can't rename old tags or delete existing ones in my tracking plan, even if they are outdated and no longer serve my purpose

Right now when one adds a source to an event, the sources appear to be arbitrarily sorted (probably by order of creation). It would be much easier to add sources if they were sorted alphabetically by default.

It is difficult to navigate through Inspector Events when you have multiple sources and need to scroll the table horizontally, because event names scroll out of view.

For Snowplow it often makes sense to have one single event that covers both a click and a view. Take an event "Internal Ad Engagement" as an example. A property e.g. "action" would then differentiate between "clicked" and "viewed". All other properties are shared between click and view. This makes data modeling a lot easier as there will be a single event schema added to the database. The self-desc event schema would be called like so: iglu:de.npg/internal_ad_engagement/jsonschema/1-0-0 To make life easier for developers on the other hand and have more concise naming, in Avo it would be better to define two separate events: "Internal Ad Viewed" and "Internal Ad Clicked" where "action" is then pinned to either "clicked" or "viewed". This would then generate two Snowplow self-describing event schemas: iglu:de.npg/internal_ad_viewed/jsonschema/1-0-0 iglu:de.npg/internal_ad_clicked/jsonschema/1-0-0 It would be great to have a feature, that allows me to create the two events, but to define that both are part of the iglu:de.npg/internal_ad_engagement/jsonschema/1-0-0 . The properties are identical for both and I'm doing this manually already. However this is very error prone as I need to copy paste the existing schema from the "Publishing" tab for either internal_ad_viewed or internal_ad_clicked and replace it with my own internal_ad_engagement.

If property A has value X then property B is required. Example: + if "Flight Type" = "Return" then "Return Date" is required + if "Flight Type" = "One-way" then "Return Date" should not be sent

Ensure to publish with the correct version increment. Currently, manual intervention is required to move a Snowplow release to production. After a publish, update Avo's pinned Snowplow schema version to match the new release. Currently, manual updating is necessary to keep Avo in sync with Snowplow's production updates.

Different eng teams rely on inspector for different things. The UI engineer cannot resolve system property violations. We want to be able to filter by property type so we can exclude system properties from the UI engineering team views.

Let's say I have created this great event property with a description and a bunch of constraints – but then I realise it should be a user property. It would be great if I could just convert it to a user property without having to define it from the scratch.

It would be useful to be able to edit comments instead of having to copy it, delete it, paste it and edit it be for posting it again.

If their team is creating a saved view, collaboratively they cannot ping the team and say they fixed this or share that a specific person is owning a group of issues to resolve. They want a way to collaborate on saying they resolved issues in inspector.