Team,
We utilize the Jira Cloud and GitHub. We have integrated Jira Deployments with GitHub deployments and utilize the .jira/environments integration to enable environments mapping between GitHub and Jira.
We do not currently utilize Jira releases or versions.
Our repository/ci-cd pipelines in GitHub are configured as a monorepo and thus we have numerous environments. These are all mapped in the the .jira/config.yaml file.
After watching the cycle time metrics and the deployments for various tickets over the last months we need some clarifications on how deployments are working. We issues that transition through a set of environments and deployments very quickly ( a few hours) but it when looking at the deployments section for that particular issue we see an array of other issues mentioned. We also see numerous deployments to production event though the issue was closed weeks ago.
I can't copy an actual issue but I'll try to recreate an example here. The issue in question we'll call CLD-1201.
Production
Pipeline | Environment | Deployment | Status | Last Updated
deploy | env-7 | changelog | Successful | 4 days ago
deploy | env-8 | changelog | Successful | 17 days ago
deploy | env-9 | changelog | Successful | 18 days ago
deploy | env-10 | changelog | Successful | 18 days ago
deploy | env-11 | changelog | Successful | 18 days ago
deploy | env-12 | changelog | Successful | 18 days ago
Staging
Pipeline | Environment | Deployment | Status | Last Updated
deploy | env-3 | CLD-1218 | Successful | 17 days ago
deploy | env-4 | changelog | Successful | 18 days ago
deploy | env-5 | changelog | Successful | 18 days ago
Testing
Pipeline | Environment | Deployment | Status | Last Updated
deploy | env-2 | CLD-1199 | Successful | 18 days ago
Development
Pipeline | Environment | Deployment | Status | Last Updated
deploy | env-1 | CLD-1198 | Successful | 18 days ago
So you can see a few things.
- This module was only deployed to environments env-2 and env-10 which is correct
- In the non-production environment didn't pick the correct "deployment"
- This issue was open and closed 18 days ago so the production deploy that is only 4 days ago blows up cycle time
Clearly we have a misconfiguration and don't understand why all this additional information is showing up? I'd expect something like the following
Production
Pipeline | Environment | Deployment | Status | Last Updated
deploy | env-10 | changelog | Successful | 18 days ago
Testing
Pipeline | Environment | Deployment | Status | Last Updated
deploy | env-2 | CLD-1199 | Successful | 18 days ago
