RELATED IDEAS
This idea has been merged into another idea. To comment or vote on this idea, please visit A-I-13274 Allow collaboration on notes and whiteboards with reviewers and viewers.
Allow Reviewers to create or edit Notes
Merged
The introduction of the Notes feature was great, my team needs a place where all our discussions and scrum meeting minutes can live. But Reviewers - who are often the type of developer/team member who is most likely to need a place for general note taking cannot create them. It sort of makes a feature which would have been really cool, inaccessible to the people who'd benefit most from it.
I understand that from a business logic level Aha wants to limit what Reviewers can do but from my and my team's perspective this might be a deal breaker. We need one source which contains all our team's work and insights. Right now there's no place for them to do that.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
1
MERGED
Allow Reviewer users to edit Notes
Need ability for my Engineering teams and leaders (who are reviewer level users) to be able to edit Notes so they can enter details without having the product managers play middle man. Notes are not a high impact object so there shouldn't be any c...
0
Shipped
I agree this design should be revisited. Cross team collaboration is essential when developing product documentation, and forcing a Contributor or Product Owner to review comments and apply edits provided by a trusted team member is inefficient.
It is also counterintuitive that a Reviewer can Create and Move a Personal Note to a Workspace and then cannot continue to edit that note. Meanwhile a contributor can make that note a personal note for themself, but cannot revert it back to the original author as a personal note.
This idea was created 6 years ago and based on the below comments, it seems like there are definitely more people asking for this feature. May be it's time to rethink your approach on this, Aha and make this a feature for the role.
I think one a key use case for us would be to keep our monthly product council meeting notes in Aha. We currently use OneNote because it gives our council members the ability to add items. As we mature with the use of the product, it would be nice to do it all in Aha.
I have users in my organization who only need the capability to edit notes. Keeping product documentation up-to-date is a collaborative process with everybody.
Echoing Ian here. We have a lot of tertiary members of the product team that we would like to be able to interact with notes. To-do and notes is cumbersome in many cases.
I think you should update your user research on this one. What is the mechanism for a "reviewer" to provide feedback if not through a note? Creating a ToDo seems clunky.
Each of the different roles within Aha! have specific permissions and capabilities. As you know, contributors and product owners are the users who have the ability to Add/edit notes. Reviewers are able view and comment on notes, as well as to create To-do's (essentially reviewing capabilities)
We are resistant to expand the capabilities of that role as we have spent time in this area based on substantial customer feedback to land at the current permissions framework where Reviewers
For this use case, your developers and additional team members can comment on the Notes (which may be useful to see conversations and thoughts from specific people), but they would not be able to add notes. I hope this makes sense.
As I have more of my team use this tool having them have the ability to add notes would be very useful.