Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-21855

Allow builds / deployments etc to be removed from an issue

XMLWordPrintable

    • 22
    • 5

    • 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

      Sometimes builds / deployments / pull requests etc. can be incorrectly associated with an issue (e.g. used the wrong issue key in a commit)

      It would be good to have the ability to remove those incorrect associations so that the linked data is correct.

       

            [JSWCLOUD-21855] Allow builds / deployments etc to be removed from an issue

            Matt Monacelli added a comment -

            Same issue here, needed to reorganize a ticket and now I can't unlink the PR from the previous ticket and it is messing up all our automation

            Matt Monacelli added a comment - Same issue here, needed to reorganize a ticket and now I can't unlink the PR from the previous ticket and it is messing up all our automation

            François Séguin added a comment - - edited

            jnavin I think that adding

             Workaround

             Currently, there is no workaround.

             

            in the issue would make it visible in https://jira.atlassian.com/browse/JRACLOUD-70206?filter=98153

            François Séguin added a comment - - edited jnavin I think that adding  Workaround  Currently, there is no workaround.   in the issue would make it visible in https://jira.atlassian.com/browse/JRACLOUD-70206?filter=98153

            Christopher Gordon added a comment -

            we would also like this feature

            Christopher Gordon added a comment - we would also like this feature

            Rachida Kebichi added a comment -

            I hit the same issue filed in this ticket. I amended the commit message and inserted the correct ID, but, the old commit stays lingering in the ticket with the message: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository". A fix to this is much appreciated.

            Rachida Kebichi added a comment - I hit the same issue filed in this ticket. I amended the commit message and inserted the correct ID, but, the old commit stays lingering in the ticket with the message: "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository". A fix to this is much appreciated.

            Vasilis Zarmpalas added a comment -

            This fix would be very helpful. 

            Vasilis Zarmpalas added a comment - This fix would be very helpful. 

            Konstantinos Pantelis added a comment -

            This has caused a lot of headache, please fix 

            Konstantinos Pantelis added a comment - This has caused a lot of headache, please fix 

            Nikolaos Sampanis added a comment -

            +1

            Nikolaos Sampanis added a comment - +1

            Byron Gkirkas added a comment -

            +1

            Byron Gkirkas added a comment - +1

            Dimitris Bousoulas added a comment -

            +1

             

            Dimitris Bousoulas added a comment - +1  

            Xenofon Dimitroulis added a comment -

            +1

            Xenofon Dimitroulis added a comment - +1

              Unassigned Unassigned
              jnavin James Navin
              Votes:
              119 Vote for this issue
              Watchers:
              66 Start watching this issue

                Created:
                Updated: