Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-115

"Move" issue notification for Jira

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Jira Cloud for Slack
    • 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.

      Supported notification triggers include issue created, issue updated, issue commented, issue transitioned to [workflow toggle].

      Suggestion:

      Add "issue moved" as a notification trigger that can be selected from the settings page.

          Form Name

            [API-115] "Move" issue notification for Jira

            Daniel Eads made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            Daniel Eads added a comment -

            This Suggestion is duplicated by API-20 in our public Jira instance. I'm closing this particular suggestion out in favor of API-20 - please move your votes and watches to that issue. Thanks!

            Daniel Eads added a comment - This Suggestion is duplicated by API-20 in our public Jira instance. I'm closing this particular suggestion out in favor of API-20 - please move your votes and watches to that issue. Thanks!
            Daniel Eads made changes -
            Link New: This issue duplicates API-20 [ API-20 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3233693 ] New: JAC Suggestion Workflow 3 [ 3588371 ]
            Trevor Thompson (Inactive) made changes -
            Link New: This issue is duplicated by API-99 [ API-99 ]
            Daniel Eads created issue -

              Unassigned Unassigned
              deads@atlassian.com Daniel Eads
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: