Automation actions to have 'same as' to copy field values

Still waiting for this automation. If should be a simple logic where we can compare two fields (fieldX same-as fieldY OR fieldX > fieldY, etc). Why is implementing this taking so long. 4 years... and still waiting....

We are adding automation to Ideas that are promoted to a feature. We have a custom field on the idea submission that we need populated on the related feature. In order to do this, we have to create an individual automation rule for each option in the custom field - which is currently at 20. Not only do is this a lot of manual work to create 20 rules, we will now have to remember to add additional automation rules if other options are added to the custom field.

I would also like to be able to set up a single automation that will copy a field from one place to another. Currently I am creating 8 different versions of the same automation.

One use case is we have certain information that is assigned at the Initiative level that we need to integrate into AzDo at the feature level. While in Aha I could do a report that links the feature to the initiative to pull the information, there is no way to get it into AzDo without automating the info onto the feature.

Similar to Deirdre's comment, I would like to automatically copy a feature's custom field to a child requirement.

Use Case explanation:

• We have created a custom field in the feature layout that defines the project charge code... this gets synched with Azure DevOps and this enables the engineers to voucher against the correct project charge code.

• What I recently realized is that most of the time the engineers are working off the requirements/user stories and therefore they are not seeing the charge code automatically in their DevOps environment.

• I want to have a charge code custom field in the requirements layout, but I want it to automatically inherit the parent feature charge code so that the Product Managers don't have to manually add charge codes to every single requirement/user story.

We really need the ability to copy a value from one field to another. 2 use cases.

• If a field on a parent record changes, we would like that to be copied to it's existing child records. That, or if a new record is created, pre-populate a couple of the parent's field values.

• We have a really big client list - and need to update another field based on the value chosen (basically, we need to parse it). But there is no way to do that today unless we create separate automation rules for each of the clients. :(

This is a good idea. If we can encourage including worksheets and custom tables in the scope it would help bring automation rules to(potentially simplify) complex structures.

We have fields on goals that we would like to cascade to all related initiatives. As the fields change on the goal, they would also change on the initiative.

It would be great to have this feature, for us we could copy the field value to another one for baselining within a certain criteria and eventually compare for performance purposes after a period of time.

Additionally we have comments we would like to carry over from features to ideas and that is not possible as we cannot copy text from one to the other. We would like to enter customer facing updates in the features and then post that exact same content on the associated idea but the automation rules do not allow for copying the text into a custom field on the ideas.

Our use case for this idea is that we are migrating to a new instance of Aha! and we want to be able to display the actual create date based on the system date of an idea or feature. When migrating that data is lost as the import will use the date of the import for the system date. As an example if we imported everything on Sept 27, then the create date will be Sept 27 even though its 3 years of data.

As a workaround we will create a custom field for create data and use the API to update that each night. It would be much better if we could set up an automation rule to populate the custom field with the date to be the same as the create date when the field is blank..

Dear Team,

This is a very simple yet powerful feature. Could you please add this to your roadmap. We cannot integrate Goal Record with JIRA Field and with the help of this idea we can atleast 'Copy' the value of Goal field value to a text and then integrate with a JIRA Custom field. This is a blocker for us. Appreciate if you could implement this asap.

Regards,

Raja Shekher Kammara

Don't understand why this wasn't part of original use-case for the automation functionality. Its simply referencing the new value in the field that kicked off the automation. You can accomplish via webhooks or API calls in other systems, would be nice to not have to do that outside setup from the tool.