Global Automation doesn't work for Team Managed projects

XMLWordPrintable

    • Minor

      Issue Summary

      When using global automation for Team Management projects, if you use the condition Issue fields condition > Issue type the automation doesn't select all the issues types IDs.
      This is reproducible on Data Center: (yes) / (no)

      Steps to Reproduce

      1. Create multiple Team Management projects
      2. Create global automation with a condition Issue fields condition > Issue type
      3. Check the database to see how many IDs match that Issue Type name
      4. Compares to the Automation JSON, it will only pick 2 issues (the global one and a random one from the Team Management project)

      Expected Results

      The automation should pick all the IDs for that issue type name

      Actual Results

      Automation only selects two issues IDs from that Issue type name (the global one and a random one from the Team Management project)

      compareValue  
      type “ID”
      modifier null
      value “[\“10143\“,\“10005\“]”
      multiValue true
      source null
      children []
      conditions []
      connectionId null

      Workaround

      For the automation runs in every Team Management Project, you need to use a condition JQL query adding the project to achieve the desired result.

            Assignee:
            Unassigned
            Reporter:
            Lígia Zanchet (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: