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

DevOps Automation: Request for a Trigger for an event "Request Changes" action in pull request

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None

    • 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.

      When any user creates a Pull request and is assigned to review, there is a new event called "Request Changes".

      Currently, there is no Trigger available in Jira Automation for this event.

            [JRACLOUD-80700] DevOps Automation: Request for a Trigger for an event "Request Changes" action in pull request

            Anusha Rutnam added a comment -
            Atlassian Update - July 2023

            After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-81390 – DevOps Automation: Bitbucket trigger when "Request changes" clicked in pull request

            We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - July 2023 After some analysis, we've found that this ticket is a duplicate of the request JRACLOUD-81390 – DevOps Automation: Bitbucket trigger when "Request changes" clicked in pull request We encourage you to watch and vote on the above instead. All internal ticket references on this ticket have been transferred. If you do not think this issue should have been closed, please add a comment here saying why and we can reopen it.

              Unassigned Unassigned
              ssingh7@atlassian.com Sugandha Singh
              Votes:
              5 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: