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

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

          Form Name

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

            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 

            We need this

            Robert Eiser added a comment - We need this

            +1

            We need this also! Please!

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

            +1 This would be very helpfull!!! 

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

            +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 ༼ つ ◕ ◕ ༽つ

            +1

            Brian Boyle added a comment - +1

            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!

            We also desperately need this. Our product is split into a number of components and I want to notify component leads when certain things occur. For this obviously an email address is needed. We only use single value components so a smart value like issue.component[0].lead.emailAddress is what is required.

            Paddy Walsh added a comment - We also desperately need this. Our product is split into a number of components and I want to notify component leads when certain things occur. For this obviously an email address is needed. We only use single value components so a smart value like issue.component [0] .lead.emailAddress is what is required.

            Jas added a comment -

            please - desperately needed!

            Jas added a comment - please - desperately needed!

            Sean Young added a comment -

            I would also like this.

            Sean Young added a comment - I would also like this.

            Please implement this, needed for many customers.

            Kalle Jämsä added a comment - Please implement this, needed for many customers.

            A customer brought this up today - their use case is to notify the Component Lead on issue create via email. Also, when the Component changes, the new Component lead should also get notified. They are not finding a way to use Smart Values for Component Leads, so this feature would be helpful.

            I'm their current TAM - I'm going to have them try the workarounds that were discussed in this Community Article: https://community.atlassian.com/t5/Jira-Software-questions/Is-it-possible-to-use-components-lead-in-Automation-for-Jira/qaq-p/1640467 and see if any of these would work in the interim.

            Dominique Cardin added a comment - A customer brought this up today - their use case is to notify the Component Lead on issue create via email. Also, when the Component changes, the new Component lead should also get notified. They are not finding a way to use Smart Values for Component Leads, so this feature would be helpful. I'm their current TAM - I'm going to have them try the workarounds that were discussed in this Community Article: https://community.atlassian.com/t5/Jira-Software-questions/Is-it-possible-to-use-components-lead-in-Automation-for-Jira/qaq-p/1640467 and see if any of these would work in the interim.

            Charlie Gavey added a comment - https://getsupport.atlassian.com/browse/JST-878655

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

                Created:
                Updated: