Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15255

Automation template "Prompt customer for comment" has the legacy scheduled trigger

      Issue Summary

      The automation template "Prompt customer for comment" has the legacy scheduled trigger

      Steps to Reproduce

      1. Access the Project settings of a Service project.
      2. On Automation, click on Library and select Prompt customer for comment.
      3. Click on the Trigger.

      Expected Results

      It should use the new scheduled trigger by default.

      Actual Results

      It shows:

      "This rule uses our legacy Scheduled trigger. Our new Scheduled trigger is easier to use, has timezone support, and the ability to preview when your rule will next run."

      Workaround

      Click on Upgrade this rule to the new Scheduled trigger and save the rule.

            [JSDCLOUD-15255] Automation template "Prompt customer for comment" has the legacy scheduled trigger

            Nicole added a comment -
            Atlassian Update - November 5, 2024

            Hi everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com.

            Thank you again for providing valuable feedback to our team!
            Jira Service Management Cloud team

            Nicole added a comment - Atlassian Update - November 5, 2024 Hi everyone, Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management Cloud users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know via raising a ticket at https://support.atlassian.com . Thank you again for providing valuable feedback to our team! Jira Service Management Cloud team

            I'm curious why this is on the Long Term backlog when AUTO-339 was pretty much the same issue and got fixed relatively quickly.  Thanks.

            Dan Breyen added a comment - I'm curious why this is on the Long Term backlog when AUTO-339 was pretty much the same issue and got fixed relatively quickly.  Thanks.

              36bd3fea80e3 Makarand Gomashe
              9454f07e6289 Rogelio Martinez Chavez
              Affected customers:
              1 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: