• Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • DVCS Connector
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      At the moment DVCS github in Jira looks for issue keys in

      • Every git commit message
      • The title of the Pull Request
      • Any Github Issues in the Repo

      In the life of a typical PR, the issue key might be overlooked during the commit and the PR creation and added later by , say, the maintainer. It will therefore be neither in the commit message nor in the title of the PR.

       

      The obvious solution is to look into the PR comments when searching for issue keys.

          Form Name

            [JSWSERVER-16674] Make JIRA look into Github PR comments for issue keys

            Gosia Kowalska made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Atlassian Update – 27 September 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 27 September 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3063794 ] New: JAC Suggestion Workflow 3 [ 3653706 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2740738 ] New: JAC Suggestion Workflow [ 3063794 ]
            BarthélémyH created issue -

              Unassigned Unassigned
              77310c41861d BarthélémyH
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: