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

Allow Conventional Commits for issue linking

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.

      Currently, the smart commit does not allow other formats of commits, for example, the Conventional Commits. It would be great to link a commit to an existing Jira issue using the Conventional Commits format.

            [JRACLOUD-90010] Allow Conventional Commits for issue linking

            Matthew Hunter added a comment -
            Atlassian Update - December 8, 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 - December 8, 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

            Kiril Daskalov added a comment -

            Try this
            Identifying JIRA tickets in conventional-commits · Issue #354 · atlassian/github-for-jira

            Kiril Daskalov added a comment - Try this Identifying JIRA tickets in conventional-commits · Issue #354 · atlassian/github-for-jira

            Michael King added a comment - - edited

            I would love it if there were a secondary way to link beyond branch name / PR name - such as Conventional commits.

            Example commit:

            feat(TD-12346): Implement some task as part of feature work #time 4h 30m implemented task 123

            I would expect to be linked to TD-12346 in Jira along with the time spent reflected on the issue's work log.

            Michael King added a comment - - edited I would love it if there were a secondary way to link beyond branch name / PR name - such as Conventional commits. Example commit: feat(TD-12346): Implement some task as part of feature work #time 4h 30m implemented task 123 I would expect to be linked to TD-12346 in Jira along with the time spent reflected on the issue's work log.

              Unassigned Unassigned
              c5c96a23be8d Bryan B (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: