Hey, we have a set of properties that every event should have. Since we’re trying to establish a flow where we create the event with it’s name, properties etc. in Amplitude Data first, then push it over to Jira using the integration, I was looking for a way to define some properties as standard properties for an event.
The goal would be that when someone creates a new event, these default properties are always there already and also cannot be removed. This is to ensure data consistency.
If this is not possible, I would be interested in how possible review/approval flows could like where a “data shepard” looks at each event that is about to be implemented to ensure it follows our guidelines.
