Allow selecting with checkboxes multiple requests and perform bulk actions on them (edit, move, delete) #3574
Replies: 3 comments 2 replies
-
Thanks for the feature request @SimonGodefroid! Technically, because a request can already be "pinned", the same concept can be used to introduce the concept of being "selected". What will need some thought and design is how to expose bulk actions in a nice manner, and just general UX patterns there. |
Beta Was this translation helpful? Give feedback.
-
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Beta Was this translation helpful? Give feedback.
-
I'm really wish this was an option right now. Previously, when I imported an OpenAPI file, it would overwrite the requests in a Collection. However, recently it's begun simply appending these requests. I'd be okay with this if I could bulk delete requests before re-importing, but it appears that there is no way to do this. |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
I am super frustrated when I imported a configuration file with 20 requests for instance or whenever actually, and I have to:
(
)* 20
When deleting a request
When moving requests under a folder (after import especially but whenever).
When changing the name of
Same if you want to change the name of a variable in request path, header and body...
e.g. here after import resource_type is a variable
but willing to manage my environment better, I choose to nest resource_type under a "global" key
Then I have to go every where and do that stuff manually meaning body, path and header
Describe the solution you'd like
Either
Make multiple selection work with Shift (just for delete)
OR
Make a button that lets appears a checkbox next to each request allowing to select it (akin to gmail inbox) and then allow to perform actions on the requests in bulk within a single environment at first.
Actions could be "Move to Folder", "Delete", "Replace variable"
and then the user could do the above and that's it.
Describe alternatives you've considered
First, fixing the OAS json to include tags property so as to map requests in folders straight from the import... but I switched context a bit because it requires different effort on my end although it's completely something that would be a game changer feature for the product.
Additional context
Beta Was this translation helpful? Give feedback.
All reactions