Jira Deployment bug

[Łukasz Śmiałowski]

1. We create a feature branch
2. When it passes Code Review and QA it gets merged with staging branch.
3. Developer deploys staging branch to staging environment (dev site) using bitbucket pipelines.
4. Jira will save that event on the timeline: OurCompany.atlassian.net/jira/software/c/projects/OurProject/deployments?startDate=-3m&endDate=now


5. At the end of the sprint we will deploy staging branch to preview theme in the production site.
6. After QA we will merge staging branch to master and deploy it to main theme (second deployment to prod env)

Tasks is marked as deployed after deploying it with bitbucket pipelines (deploy settings on) and then, after sometimes due to the new deploy of another branch and commits (as we suppose) task is once again marked as deployed, could you somehow help us on it? 

[Andy Heinzer]

Hi Lukasz,

I'm not sure I understand the concern here.  I believe it revolves around some issues within Jira that might appear to be marked as deployed more than once due to the different environments. There is also our documentation guide for this feature in Company managed projects over in Integrate your deployments with Jira, but of course if this is not sufficient to help here, I want to learn more so we can try to help here.

Could you please let me know what behavior you are expecting here versus what behavior you are seeing.  This is a still relatively new feature within Jira Cloud so I want to make sure that I understand the desired behavior here juxtaposed against the actual behavior so that I can investigate this further. 

Thanks

Andy