Copy all existing custom field values when promoting the work request
When promoting the Work Request to an object, copy all existing custom field values that are shared across all Ideas (with same API key) from the originating object to the new object
Guest
Jul 16, 2025
This feature is absolutely needed. It's tedious to have the recipient product manager to copy/paste content from the originating work request. The copy/paste of the description helps. Please include copying all attachments and comments from the originating work request to the created object in the receiving workspace.
My product is a cross platform product (think shared service) & often there is work for multiple products to do to support the work my product needs. We need all the value fields, along with the description to carry w/the To-Do Epic or Feature when sent to another area. I need to keep my item on my board for tracking and I need an exact duplicate added to their board so I know they understand everything about my item.
Telling another Product Owner or Product Director that they have to sit and copy/paste multiple fields into the work item after they accept it, is wasteful, inefficient and just not what would be expected from a product like Aha built for Product Management.
https://big.ideas.aha.io/ideas/A-I-14172 these tickets need to be grouped. The two way mirror is absolutely necessary, if not you should just move the ticket to a different workspace and create a report.
This is a key feature that is needed. Work requests are great, but when the originating record contains all the accurate information, it becomes tedious for the recipient to accept the work request and ensure their record contains the same information. This is causing our Product Management team to have inconsistencies, slowing down the process and causing unnecessary admin work to update the accepted record accurately
When accepting a work request, allow fields with same API_key to carry over from requesting record to new record
Merged
Who would benefit? Product Owners and Cross Functional Teams What impact would it make? Eliminate having to copy information from 'depends on' records into 'dependency of' records How should it work? It would work like it does when promoting ideas...
Guest
over 1 year ago
in To-dos
0
Future consideration
1
MERGED
Allow for mentioning of specific fields
Merged
What is the challenge? When working across multiple workspaces, I sometimes make to-dos or work requests for a given feature. The receiving workspace cannot easily see all aspects of information I would like for them to see, which creates duplicat...
Guest
about 1 year ago
in To-dos
0
Future consideration
This feature is absolutely needed. It's tedious to have the recipient product manager to copy/paste content from the originating work request. The copy/paste of the description helps. Please include copying all attachments and comments from the originating work request to the created object in the receiving workspace.
My product is a cross platform product (think shared service) & often there is work for multiple products to do to support the work my product needs. We need all the value fields, along with the description to carry w/the To-Do Epic or Feature when sent to another area. I need to keep my item on my board for tracking and I need an exact duplicate added to their board so I know they understand everything about my item.
Telling another Product Owner or Product Director that they have to sit and copy/paste multiple fields into the work item after they accept it, is wasteful, inefficient and just not what would be expected from a product like Aha built for Product Management.
https://big.ideas.aha.io/ideas/A-I-14172 these tickets need to be grouped. The two way mirror is absolutely necessary, if not you should just move the ticket to a different workspace and create a report.
100% need this asap.
absolutely needed. Please prioritize this if possible
I agree with Danielle this is a key feature needed.
Please include Attachments in this request. Thank you!
This is a key feature that is needed. Work requests are great, but when the originating record contains all the accurate information, it becomes tedious for the recipient to accept the work request and ensure their record contains the same information. This is causing our Product Management team to have inconsistencies, slowing down the process and causing unnecessary admin work to update the accepted record accurately