Prevent duplicate records from being created when multiple Jira webhooks are received for same new parent record

Use case:

• Multiple records in Jira do not have parent records; they are updated at the same time in Jira to add the same parent record (e.g. bulk edit)

• As a result of the change in Jira, we receive 2 webhooks into Aha! at the same time

• Since both webhooks result in Aha! determining there's no parent in Aha! -- this results in duplicate parent records being created in Aha!

• Duplicate records being created in Aha!

• This requires manual work to identify and resolve when this situation arises

• Aha! should prevent duplicate records from being created when receiving webhooks at the same time

• In situations where the webhooks may span workspaces/Jira projects, an integration update may be best to allow a user to choose the workspace for where to create the parent record