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

JSM automation - Unable to set the request type for cloned issues within automation branches

XMLWordPrintable

      Steps to Reproduce

      1. Create an automation rule based on any trigger.
      2. Add a "Then" statement to clone this issue into another JSM project.
      3. Add a "For all created issues" branch.
      4. Add a "Edit request type of this issue" function, to edit the clone's request type.

      Expected Results

      The dropdown will display a list with the available request type for the clone/destination project.

      Actual Results

      No options will be displayed.

      Workaround

      No workaround at the moment.

        1. image-2021-10-27-17-20-44-260.png
          image-2021-10-27-17-20-44-260.png
          89 kB
        2. image-2021-10-29-13-24-07-086.png
          image-2021-10-29-13-24-07-086.png
          260 kB
        3. image-2021-11-03-14-43-29-718.png
          image-2021-11-03-14-43-29-718.png
          30 kB
        4. screenshot-1.png
          screenshot-1.png
          224 kB
        5. screenshot-2.png
          screenshot-2.png
          204 kB
        6. screenshot-3.png
          screenshot-3.png
          218 kB

            [JSDCLOUD-15084] JSM automation - Unable to set the request type for cloned issues within automation branches

            Zach Taylor added a comment -

            Well, that's extremely concerning! We are experiencing this exact issue nearly 3 years later and not even a workaround exists!? What's the deal Atlassian?

            Zach Taylor added a comment - Well, that's extremely concerning! We are experiencing this exact issue nearly 3 years later and not even a workaround exists!? What's the deal Atlassian?

            Ryan Gillespie added a comment -

            Do we even know why this affects our site? Other people have screenshots of it just working. I do an identical thing and that whole option refuses to work and so far there is no workaround. It appears that no matter what I do in automation, the cust req types options are empty. Even if I make a brand new rule with just "when issue is commented" then go to edit cust req type, the list remains empty.

            Ryan Gillespie added a comment - Do we even know why this affects our site? Other people have screenshots of it just working. I do an identical thing and that whole option refuses to work and so far there is no workaround. It appears that no matter what I do in automation, the cust req types options are empty. Even if I make a brand new rule with just "when issue is commented" then go to edit cust req type, the list remains empty.

              36bd3fea80e3 Makarand Gomashe
              pjunior Paulo Junior (Inactive)
              Affected customers:
              5 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: