Need a feature to detect skipped deployment stages & ingest events for skipped deployment stages in case of Jira Azure DevOps integration.

Currently, when we integrate Azure DevOps with Jira and sync development data into Jira work items' development info panel, there are scenarios where a stage is skipped during development efforts and due to this the specific pipeline events, such as run started, run completed, or stage completed are not executed. 

For example: We created a commit and associated it with Jira Work item JW-1, but we didn't perform any deployment, thus the stage was skipped. Then, I created another commit and associated it with Jira Work item JW-2, but this time I performed deployment. 
So after this deployment, if you go to let's say JW-1 work item, check the dev info panel and look for the deployment tab, you will not see the deployment. But if you go to JW-2 work item, check the dev info panel and look for the deployment tab, you will be able to see the deployment data.
Ideally, we should be able to see the deployment in the dev info panel>>deployment tab for both the Jira Work items. 

This behaviour is because we didn't perform deployment after the commit was done i.e. we skipped the deployment stage &  If the stage is skipped, the Azure DevOps webhook doesn’t emit an event. As Azure DevOps do not emit an event, so Jira cannot ingest the event. This is a known behaviour of Azure Devops Pipelines.