Skip to main content

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.

Hi @lars 

You can try Property Groups for better grouping and applying the set of repeated properties for easier management of your tracking plan.

But this is just a UI based approach in Amplitude Data and the actual implementation of sending repeated/default set of properties on your events will have to be handled by your instrumentation code.

Hope this helps.


@Saish Redkar that’s clear. However, we’re aiming for a workflow where we define the event in Amplitude first, then push it over to Jira using the integration.


Reply