Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-485

Automation support for working with components and component leads - new triggers, actions and smart values

XMLWordPrintable

    • 0

    • 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.

      Suggested improvements

      • Right now only component names can be accessed with Jira Automations. A sample Use Case would be to create sub-tasks for every component added to an issue and assigning their component lead to those. Accessing to the component lead could be possible like this: { {issue.fields.component.lead.displayName}

        . Right now this is not possible without an API call which is taking way longer and is much more complicated and much more prone to error.

      • Include project components create/edit actions as a trigger - Support to configure rule triggers based on project component create/edit actions so automation rules can be used to configure action upon that activity.

            [AUTO-485] Automation support for working with components and component leads - new triggers, actions and smart values

            deepika.bhangole added a comment -

            I need this as we are actively using components, but lack the feature to enable them for automation 

            deepika.bhangole added a comment - I need this as we are actively using components, but lack the feature to enable them for automation 

            Robert Eiser added a comment -

            We need this

            Robert Eiser added a comment - We need this

            sibel.avci@xprclub.com added a comment -

            +1

            sibel.avci@xprclub.com added a comment - +1

            Hynynen Mari added a comment -

            We need this also! Please!

            Hynynen Mari added a comment - We need this also! Please!

            Pierre Laaser [K15t] added a comment -

            +1 This would be very helpfull!!! 

            Pierre Laaser [K15t] added a comment - +1 This would be very helpfull!!! 

            Nikolay Salin added a comment -

            +1

            Nikolay Salin added a comment - +1

            Levi Graff added a comment -

            For anyone still trying to do this, there's a workaround; If your project defaults to unassigned, and you have only one component per issue, if you set the "Default Assignee" property to "Component lead (LEAD_USER)", Jira will automatically assign that issue to the Component Lead.

            Levi Graff added a comment - For anyone still trying to do this, there's a workaround; If your project defaults to unassigned, and you have only one component per issue, if you set the "Default Assignee" property to "Component lead (LEAD_USER)", Jira will automatically assign that issue to the Component Lead.

            Levi Graff added a comment - - edited

            ༼ つ ◕◕ ༽つ GIVE US COMPONENTS/LEADS ༼ つ ◕◕ ༽つ

            Levi Graff added a comment - - edited ༼ つ ◕ ◕ ༽つ GIVE US COMPONENTS/LEADS ༼ つ ◕ ◕ ༽つ

            Brian Boyle added a comment -

            +1

            Brian Boyle added a comment - +1

            Sandra.Abi-Khalil added a comment -

            Is there any way of knowing if we can hope for this to happen soon? It's much needed!

            Sandra.Abi-Khalil added a comment - Is there any way of knowing if we can hope for this to happen soon? It's much needed!

              ksilver Katie Silver
              4413169a7af2 Jan Schneider
              Votes:
              191 Vote for this issue
              Watchers:
              81 Start watching this issue

                Created:
                Updated: