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

Ability to enforce Pull Requests on Github to be linked to a Jira issue

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.

      We would like to have this functionality to enforce that the Pull Requests on Github raised are linked to a Jira issue, in order to it to be created.

            [JRACLOUD-90028] Ability to enforce Pull Requests on Github to be linked to a Jira issue

            Matthew Hunter added a comment -
            Atlassian Update - October 31, 2024

            Hi everyone,

            Thank you for bringing this suggestion to our attention. As explained in our new feature policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.

            Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it.

            While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.

            Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Matthew Hunter added a comment - Atlassian Update - October 31, 2024 Hi everyone, Thank you for bringing this suggestion to our attention. As explained in our new feature policy , there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritise and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order. Unfortunately, as a result of inactivity for an extended period of time, this suggestion didn’t make it to the roadmap and we are closing it. While this issue has been closed, our Product Managers continue to look at requests on jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket. Thank you again for providing valuable feedback to our team - Jira Cloud Product Management

            Dhiren Notani_Exalate_ added a comment - - edited

            Hi Diego,
            This is Dhiren from Team Exalate
            If you want to sync GitHub Pull Request to a Jira Issue then I would recommend you to use an Integration solution like Exalate.
            With the script mode provided by Exalate (which is based on Groovy), you get a lot of customization and flexibility.
            You can also sync GH issues with Jira Issues bi-directionally!
            Thanks, Dhiren

            Dhiren Notani_Exalate_ added a comment - - edited Hi Diego, This is Dhiren from Team Exalate If you want to sync GitHub Pull Request to a Jira Issue then I would recommend you to use an Integration solution like Exalate . With the script mode provided by Exalate (which is based on Groovy), you get a lot of customization and flexibility. You can also sync GH issues with Jira Issues bi-directionally! Thanks, Dhiren

              Unassigned Unassigned
              8e2ee97d25b6 Diego Leitão
              Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: