[Feature-Request] Allow Users to Mark Requests as Favorites with Optional User Image and Tagging Capabilities

[devmontini]

Is there an existing request for this feature?

• I have searched the existing issues for this feature request and I know that duplicates will be closed

Is your feature request related to a problem?

Yes, in collaborative environments where multiple team members work on the same Postman workspace, it can be challenging to quickly identify and share important requests. Users often have to manually search or rely on naming conventions to find frequently used or critical requests. This can lead to inefficiencies and miscommunication within the team.

Describe the solution you'd like

I would like to implement a feature in Postman that allows users to mark requests as favorites. When a request is marked as a favorite, an optional user image can be displayed next to the request to indicate who favorited it. Additionally, users should be able to tag other team members within the same workspace to highlight important requests. Only the tagged team members should be able to see the requests they were tagged in, ensuring that such highlights are private to the intended individuals. Alternatively, there should be an option to mark a request as a favorite that is visible to everyone in the workspace. If no team members are tagged and the request is set as visible to all, it will be marked as a general favorite. Maybe this feature should include options to manage and view these favorites and tagged requests in a dedicated section, making it simple to access frequently used requests and enhance collaboration within the workspace.

Describe alternatives you've considered

Using Request Naming Conventions: One alternative considered was enforcing strict naming conventions for requests to help team members identify important ones. However, this approach relies heavily on team discipline and can be inconsistent, leading to confusion.

Creating a Shared Documentation File: Another option was maintaining a shared document or Notion page where team members list and categorize important requests. While this could work, it adds an extra step to the workflow and doesn't integrate seamlessly into Postman, making it less efficient.

Labels or Tags: Introducing a simple tagging system without the option to mark as favorites or include user images was also considered. However, this would lack the personalized and collaborative aspect that the favorite-marking feature provides.

Additional context

To illustrate the need for this feature, I’ve included a screenshot of our current workaround. Currently, we use * to manage important requests, which is less efficient and lacks the collaborative functionality we're proposing. This image shows how we’re manually handling it: