Avo
Create
Log in
Sign up
Home
Feedback
Avo Feature Requests
339
Changelog
Boards
Avo Feature Requests
Bug Reports
Powered by Canny
Avo Feature Requests
Please be as specific as you can and include your use case 🙌
💡 Pro tip: Before you submit, search existing ones for a discussion on the same subject.
Details
Showing
Trending
Sort
Trending
Top
New
Filter
Under Review
Planned
In Progress
Complete
posts
Assigning events to a domain should require a review
We have a lot of admins and it seems any one can unilaterally change domain assignment for events. This is something that we'd like to have approval for. Assignment to domains should work similarly as assignment to categories.
0
2
Requested Reviewers should be notified in the app that an approval is needed for an change to events in their domain
Currently, Avo only sends emails and slack notifications when you are requested for a review. A notification in-app and/or a list of open reviews they have been requested for would also be extremely beneficial.
0
2
Impacted Stakeholders should be automatically added to a review
Notifying the user changing an event that some changes impact certain domains/stakeholders isn't enough to prevent those changes from going through. It should not be up to the user making the changes to opt-in to including impacted stakeholders.
0
2
Changes to events assigned to a stakeholder domain should require an approval before branch merge from at least one representative per impacted domain
There are a lot of events we have that are relevant to more than one domain. We need input (or at least approval) from each impacted domain before we can move forward with a merge. Since Avo doesn't currently automatically add impacted stakeholders to the branch review, requiring at least one representative per domain for approval before merge is allowed would prevent users from 'forgetting' to include representation for all impacted stakeholders on a review.
0
2
Any detail changes to an event should trigger that stakeholders have been impacted
Currently, changes to some fields (at least Description possibly more) don't trigger the notification that stakeholders have been impacted by a change to one of their domains events. Any change should trigger that notification. There is a lot of care that goes into all aspects of an event, description included, that need to be agreed upon when changes are offered.
0
2
More environments for Inspector
We would love more place to connect inspector than Dev, Prod, Staging. Gaming has more environments for testing and they would like the ability to add more environments.
0
1
Prevent properties from going to certain destinations
It would be useful to be able to prevent properties from going to certain destinations. For example PII that are useful for one destiantion but are not allowed to go to others.
0
14
Inspector: Detect and alert event volume drops and spikes
It would be useful of Inspector would detect significant event volume drops and spikes, for example between versions. And even better if it would alert me!
2
14
Bulk edit Inspector issues
Make it possible to bulk edit (e.g. update the status) of multiple Inspector issues at once.
0
2
Revert branches
I'd like to be able to revert changes made on main after a branch was merged–and re-open the branch so I can make adjustments before merging again.
1
11
Load More
→
Powered by Canny