When we go through planning cycles, we find ourselves updating a dozen fields for each idea or each potential initiative to help in prioritization. Our team still tend to do this in Google Sheets / Excel, because it's much faster to make the edits quickly on one screen, tabbing through each field. We can then import our spreadsheet, but this isn't good for round-tripping, and it means that we're working in multiple tools (Google Sheets + Aha!).
We would like to see a view in Aha! like the list view that allows us to quickly update a set of fields (columns), without having to open each idea / initiative.
We have now added an edit mode toggle, so that you can switch your list reports into an editable version, with extra fields and interactions, and then go back to viewing a more concise list.
Love it!
Here is an example from our demo site Fredwin cycling.
List mode
Edit mode
Some fields are not editable for a number of reasons, such as:
You don't have edit permissions for that record / workspace
The data is automatically calculated - feature progress is calculated from the progress of it's children.
thanks for this. I chose Edit mode but I dont see fields are editable still. Can Aha! support or SMEs show a video of this ?
Our Product team frequently needs to update fields on the Epic (status, dates, custom fields, etc.) as they review them. Today, when reviewing a report, users must open each individual record to make a simple edit. This is slow, repetitive, and interrupts flow.
Tools like Asana, Monday.com, Airtable, and Smartsheet all allow inline editing, where fields can be updated directly from the report/table view without opening the underlying record. This is the #1 reason I have difficulty getting adoption of Aha within the product team.
Honestly, after 10 years, this feature should be delivered. It's a big gap.
We review the epic & idea prioritization board with various internal team on a weekly basis. During that session, we do perform some quick updates, be it adding a note, changing the status, changing the release, interacting with custom fields. In order to perform those actions, if we have to open the ticket each time, that adds extra steps.
Grid edit function is desperately needed. Similar to the other use case mentioned there are multiple scenarios where view can be created to narrow down to a particular subset of data and make multiple fields across multiple records. Tee only method to make multiple edits for multiple fields do that now is to export a csv file, format and make edits, and then go through the import cycle, assign fields, etc. The efficiencies gained in having a single data set, and all of the features in Aha! are lost by the additional cycles in data management.
Yes, I've used the bulk edit features in the past, but it's only helpful when i want to assign the same value to multiple features at once. The use case I describe here is different, because I'm going down a list of features (or ideas or initiatives) and assigning different values based on an assessment of that feature.
Thanks for the note. We've updated the idea to "Likely to implement."
Have you seen the bulk editing capabilities on the Features and Ideas list pages? While this does not completely solve your problem, it may be helpful in some respects.