RELATED IDEAS
Automation actions to have 'same as' to copy field values
Currently if I need pass on a field value from one field to another, there is no easy way, but to create separate automation rule for each value. Which is not optimal and will have to create 10 rules for 10 values and if a new value is entered need to remember to add another rule.
Instead there should be a provision to use 'Same as' to pass values from one field to another.
-
ADMIN RESPONSEMay 10, 2023
We have recently added improvements to automation rules.
You can now create an automation rule that will:
Update a date field to be based on a different date field.
Update a feature's initiative to be the same as its epic's initiative.
We will keep this idea open to monitor feedback on other fields you would like to reference. Please add a comment with your use case.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +45
1
MERGED
Assign values to Custom fields from other standard or custom field content in automations
What is the challenge? When creating automations (and in worksheet fields): when a trigger is activated or eg specific criteria is true/false, I want to assign values to custom fields from standard or other custom field content. What is the impact...
0
Future consideration
12
MERGED
Automation Rules: Allow a Custom field of a related record to be updated to "MATCH"
We want to set an Automation Rule that will automatically set the value of a custom field at the feature level to "Match" the value in a custom field on the Epic. We also want the ability to make the value unchangeable on the feature - which we ca...
2
Future consideration
10
MERGED
Automation rules should allow passing a value from one field to another field
Want to be able to Pass eg; values from categories to a custom field either on Ideas or features based on a condition instead of setting rules for each value of the category. So if I have 10 value in my category, I have be build 10 different rules...
0
Future consideration
3
MERGED
14
MERGED
Ability to dynamically add individuals to automation email TO: based on fields
Like you can do with To-dos, you can assign automation items based on user fields, i.e. assigned to and custom user fields like BA, UX, Developer, etc. We would like to be able to do the same with automation emails so that these can be targeted to...
2
Future consideration
7
MERGED
Automation be able to select other field's value
I would like to be able to sync up the release date field with the external release date. When I use automation to try to do this, I am only able to select the current date or a date based on the current date. I would like to be able to set it as ...
1
Future consideration
7
MERGED
Ability to set one field to another field's value in automations
It would be helpful in automations to support the ability to set the value of one field be equal to the value of another field. For example: On an idea, I have a custom "Goals" field. My product managers set this field when an idea is raised to al...
0
Future consideration
16
MERGED
Automation: As part of the "Action" clause, when using the "update the field" option, I want to set the field to be "the same as" another field
As an example, when I add a feature to an epic, I want to automatically update the goal and initiative of the feature to be "the same as" the epic. Another example: idea categories can't be carried over to features. I might create a custom field i...
1
Future consideration
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.