Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-4373

Incorrect Notification Helper for Issue Moved

XMLWordPrintable

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      Summary

      Currently, Reporter doesn't receive notification for Issue Moved event. This is expected as per:

      However, Notification Helper says that Reporter receives notification. Though this is also expected according to JIRA's Default Notification Scheme, it's confusing.

      Steps to reproduce

      1. Create 2 SD projects A and B
      2. Create a customer C and ensure C has access to both A and B
      3. As customer C, create a request in A
      4. As an agent, move the request to B

      Expected behavior

      C doesn't receive notification and Notification Helper should explain why.

      Actual behavior

      C doesn't receive notification but Notification Helper says it should.

      Note

      It has been suggested that customers receive notification for Issue Moved event. This is currently being tracked in JSD-3417.

            [JSDSERVER-4373] Incorrect Notification Helper for Issue Moved

            Ishwinder Kaur added a comment -
            Atlassian Update - 03 March 2025

            Hi,

            At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.

            This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.

            We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs.

            To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.

            Kind regards,
            Jira Service Management Data Center

            Ishwinder Kaur added a comment - Atlassian Update - 03 March 2025 Hi, At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products. This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact. We appreciate your time in submitting bugs to our product team and encourage you to continue doing so. Many features and functions in our products come from valued customers such as yourself. You can read more about our bug fix policy here and how we prioritize bugs. To learn more about our recent investments in Jira Service Management Data Center, please check our public roadmap and dashboards containing recently resolved issues , current work, and future plans . Kind regards, Jira Service Management Data Center

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: