Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-89991

Deleted the Production env from github repo settings, and still can see that being reflected in Jira "deployments" tab

XMLWordPrintable

    • 1

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Issue Summary

      Deleted the Production env from github repo settings, and still can see that being reflected in Jira "deployments" tab

      Steps to Reproduce

      1. Created a commit to trigger a deployment
      2. Deployment got registered into the ticket
      3. Delete that particular envinronment from github repo setting

      Expected Results

      Deployment would be removed from https://github.com/<workspace>/<repo>/deployments and in the Jira ticket for the deleted environment

      Actual Results

      Deleted that particular environment from github repo settings

      • I can still see that deployment in https://github.com/<workspace>/<repo>/deployments (not tagged to any env)
        and it still reflects in my Jira ticket
      • Still reflects in my KAN-10 ticket

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

            [JRACLOUD-89991] Deleted the Production env from github repo settings, and still can see that being reflected in Jira "deployments" tab

            Dimitri Gamkrelidze added a comment -

            Keeping track of environments is crucial for QA to plan and run tests smoothly. Right now, the lack of sync between GitHub and Jira can mess us up by having us test in the wrong or outdated environment, which hurts our ability to guarantee quality. 

            Dimitri Gamkrelidze added a comment - Keeping track of environments is crucial for QA to plan and run tests smoothly. Right now, the lack of sync between GitHub and Jira can mess us up by having us test in the wrong or outdated environment, which hurts our ability to guarantee quality. 

            Lucas Cheles added a comment -

            The ability to automatically synchronize Jira to reflect changes made in GitHub environments is crucial for maintaining accurate project tracking and management. Currently, when an environment is removed from GitHub, it continues to appear in Jira, leading to discrepancies that can confuse team members and misrepresent the actual state of deployments. This can cause issues in understanding the deployment lifecycle and operational status, which are critical for timely decision-making and maintaining workflow efficiency. Implementing a feature that ensures synchronization between GitHub and Jira will enhance transparency, reduce the risk of errors, and improve overall project management efficiency. 

            Lucas Cheles added a comment - The ability to automatically synchronize Jira to reflect changes made in GitHub environments is crucial for maintaining accurate project tracking and management. Currently, when an environment is removed from GitHub, it continues to appear in Jira, leading to discrepancies that can confuse team members and misrepresent the actual state of deployments. This can cause issues in understanding the deployment lifecycle and operational status, which are critical for timely decision-making and maintaining workflow efficiency. Implementing a feature that ensures synchronization between GitHub and Jira will enhance transparency, reduce the risk of errors, and improve overall project management efficiency. 

              Unassigned Unassigned
              90ba31140975 Josh H
              Votes:
              2 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: