We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

    • 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 Pull Request webhook payload does not include a specific object to list the Jira issues that were linked in the commits of the Pull Request or Pull Request title. The issue key is only returned in the payload if it's part of the title of the pull request.

      However, this prevents the usage of the Pull Request webhooks to trigger Jira automation( e.g automatically move a ticket to a certain state) as Jira looks specifically for an issues array in the JSON object like the below : 

      {
        "issues": [
          "TEST-123",
          "TEST-124",
          "10023"
        ]
      } 

      This feature request is to implement a separate issues objects to be returned as part of the Pull Request webhook payload, containing all the issues that are part of the Pull Request commits/branches/title.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

              • 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 Pull Request webhook payload does not include a specific object to list the Jira issues that were linked in the commits of the Pull Request or Pull Request title. The issue key is only returned in the payload if it's part of the title of the pull request.

                However, this prevents the usage of the Pull Request webhooks to trigger Jira automation( e.g automatically move a ticket to a certain state) as Jira looks specifically for an issues array in the JSON object like the below : 

                {
                  "issues": [
                    "TEST-123",
                    "TEST-124",
                    "10023"
                  ]
                } 

                This feature request is to implement a separate issues objects to be returned as part of the Pull Request webhook payload, containing all the issues that are part of the Pull Request commits/branches/title.

                        Unassigned Unassigned
                        641e77b2eb21 Patrik S
                        Votes:
                        14 Vote for this issue
                        Watchers:
                        10 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            641e77b2eb21 Patrik S
                            Votes:
                            14 Vote for this issue
                            Watchers:
                            10 Start watching this issue

                              Created:
                              Updated: