I am a fan of Bookmarks in Studio, but I would love to see more advanced features for them.
We are using Bookmarks to review code changes and provide feedback for the developer before a branch is merged to production.
Often a screenshot could save a lot of written text.
For example if you need to point out 3 specific properties for an activity that has several, then it is sometimes easier to take a screenshot and highlight the 3 properties, rather than trying to describe it specificly.
Also the option to format text with bold, italic, underline etc. would prove useful.
So what I am wishing for is some sort of advanced editor for Bookmarks.
And of course the “mouse over display” of the bookmarks should support this aswell.
I know that the message for Bookmarks is intended to be short and precise, but I dont think that these added features would change that.
It would simply make it easier to create useful expressive messages.
Love this feature and your feedback @SorenB @Raluca_Laic
I see bookmarks to be used for initial code reviews. This feature allows us to directly add comments on specific steps within the code, eliminating the need for extensive documentation, capturing screenshots, and manually searching through workflows/activities to check if developers have implemented the recommended changes.
Implementing a system where we can mark these bookmarks as ‘Completed’ once the suggested modifications are made would be incredibly beneficial. This would not only help in tracking the progress of code corrections but also ensure a more organized and effective review process.
It would be great if bookmarks could be defined on a “deeper level” like properties, within parameter definition (like headers/parameters on HTTP Request), variables and arguments.
Also it would be nice to have 3 “states” for the bookmarks - created, solved and closed. In this way the developer can address the issue from the reviewer, solve it, and still be visible to the reviewer afterwards (for check up).
Hi,
The new message from SorenB describes an ideal scenario (Bullet Point 2); I think the reviewer can take the decisions of removing them after item is marked as ‘closed’ or keep it there, I would say this could be flexible to avoid delivering products with many bookmarks/comments to the end client - many bookmarks/comments will raise a concern related to development lack of experience.
