Feature request: Add multiselect option for exporting

[ambrusfi]

Hi all,

while option to export a single API call is really useful, we see the need for adding a multiselect option.

As a QA I'm well aware of which specific API call I need to observe and, possibly, export but we run into issues when someone who isn't fully accustomed with API calls is also performing testing. This is usually a case when a client is performing user acceptance testing.

In those situations, to avoid multiple ping-pongs between us and the client where we are asking for API call examples and they are sending the wrong ones, it would be great to have a multiselect option.

In that case, they would be able to select multiple API calls, export them as separate files and share them with us.

This would work similar to instant messaging or email apps where you are able to select multiple messages/emails by long press and having a share icon in the top right corner.

I'm open to any other suggestions from your side.

:raising_hand: Do you want to develop this feature yourself?

• [ ] Yes
• [x] No

[vbuberen]

Hi @ambrusfi Thanks for a feature suggestion.

Initially I wanted to ask if exporting all transactions might cover at least some cases for you. But after seeing so many likes I believe we would just add this feature into our to-do list 😄

[cortinico]

Thanks for your feature request @ambrusfi

In those situations, to avoid multiple ping-pongs between us and the client where we are asking for API call examples and they are sending the wrong ones, it would be great to have a multiselect option.

Just as a curiosity, how a multi-select feature will mitigate this? If the client is sending you the wrong ones, it will potentially multi-select wrong call, no?

Also as @vbuberen, the export all feature sounds like a good solution to your use case. Have you tried it?

[ambrusfi]

Thanks for your feature request @ambrusfi

In those situations, to avoid multiple ping-pongs between us and the client where we are asking for API call examples and they are sending the wrong ones, it would be great to have a multiselect option.

Just as a curiosity, how a multi-select feature will mitigate this? If the client is sending you the wrong ones, it will potentially multi-select wrong call, no?

Also as @vbuberen, the export all feature sounds like a good solution to your use case. Have you tried it?

Hi @cortinico , sorry for being a bit unclear here, but the usual scenario is as follows:

1. client report a bug
2. we request a sample of API call that failed
3. client tries to guess which API call he needs to send as he is not accustomed in reading them so he sends a wrong one, or worse, sends a screenshot of all API calls because he doesn't want to lose time and export one by one
4. we ask for additional logs and the loop continues

If we were to have a multiselect option, client would be able to multiselect all API calls and send them to us in one go. Then we would sniff trough it and find the right one(s).

The biggest issue we have here is the fact that often some actions require executing multiple API calls and exporting them one by one takes a long time.

Export all feature would be beneficial for this case, but I believe implementing this would also help us as a QA to quickly and easily export multiple specific API calls when reporting an issue to a developer.

[vbuberen]

Thanks for additional explanations.

3. sends a screenshot of all API calls because he doesn't want to lose time and export one by one

From your description it looks like you or your clients aren't aware that we already have export all feature. If so, take a look at share icon on the main Chucker screen - this is the button your clients need to export all transactions (see the attached screenshot).

If we were to have a multiselect option, client would be able to multiselect all API calls and send them to us in one go. Then we would sniff trough it and find the right one(s).

How multiselect resolves the issue with client tries to to guess which API call he needs to send?