RELATED IDEAS
Include Admin Response in the Bulk Edit of Ideas
When an issue is assigned to a release, I add an Admin Response indicating when the item will be made available. It would be extremely helpful to be able to bulk update the Admin Response for all ideas whose corresponding features have been assigned to a specific release. Currently I have to go into each idea, and it is time consuming.
-
ADMIN RESPONSEOct 7, 2024
You can now add an admin response to multiple ideas at once with bulk edit. In any idea list report, select the ideas to update, then click the Bulk edit button. Add your admin response and optionally check the box at the bottom to send notifications to the idea subscribers.
9
MERGED
Ability to bulk edit idea Admin Message
Who would benefit? PMs having to make same update to list of ideas after release What impact would it make? Save time and deliver consistent message. How should it work? After a release of a new version of a product we often have long lists of ide...
0
Shipped
1
MERGED
© 2024 Aha! Labs Inc.•All rights reserved
I have found a "workaround" to this. Using automation rules, I am able to set an Admin Response to trigger when I add a specific tag to the idea. I have had to do some bulk responses to ideas, and this has worked out well. It's also nice because you could turn it on/off when you want, and even edit the tag used to trigger the automation and the Admin Response verbiage accordingly in between batches of work.
Once I have the automation set up, I go into my list report and bulk edit the selection of ideas to add the trigger tag. After that bulk edit finishes, the Admin Responses are added to the idea automatically (you can double check the ideas or the automation rule as it counts how many times it has run, or if there are errors!
You could likely use other functions of the automation to trigger it, this is just what's worked for me.
You may be interested in adding the new "Promoted release name" field to your ideas portal. After an idea ships, this field will display the name of the release that contained the work. For example, if the idea was promoted to a feature, it will show the release name that feature is assigned to. You can learn more here.
There is not currently a way to pull this release name into an admin response with automations, but that is a good idea.
With automation I can now announce an idea is available when a Release is moved to the Shipped status. Fantastic. What is even better for customers if we could pipe in information instead of a generic message that is used for every release - i.e "Great news! Your idea has been delivered". Now go off and figure it out where and when it was delivered.
For example if my release is called 4Q2023 or 4.7.1 then have the ability for the Admin Message to point to that release so a customer can find it and implement it. Automation would trigger based on the Release moving to Shipped and updating all associated ideas to move to Delivered state. Once in the Delivered state an Idea automation is triggered to update the Admin Message. How can the admin message be automated to pull data or display such as what is in the Release field?
This is key to efficiently handling our ideas portal, especially when classifying multiple ideas as "not planned", in our case we have a policy that if the idea didn't receive X number of votes in X period will not be planned.
We need this badly to update 40+ Ideas all at once, per week.