We've automation triggers from issues to send data to our data lake.
One of automation is issue deleted, but when this automation runs another line is created in our database, but I can't identify some information about this issue was deleted, and when some team are quering the data this issue ends up being counted along with the others issues.
Does anyone knows how can I identify issues deleted?
Hi @Alex Koxaras , thanks!!!
When the issue is deleted and the automation for issue deleted runs, I receive the event in our data lake, but this new data we'd not been able to identify some information that show us that this data means that has been deleted on Jira.
We have a lot of Jira projects on our company, and some projects are big.
case of example:
In June 22, we receive a lot of data cames with the automation, and when I count distinct keys we have 4k.
But 70 keys have been deleted in Jira.
Automation doesn't delete this issues in our datalake, automation send an event, but this new data we'd not been able to identify some information that show us that this data means that has been deleted on Jira.
And when the final user querying the data they can do a false positive, coz they didn't know which key is deleted.
Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...