New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order of requests inside folders changes after collection merge #5814
Comments
+1 This is incredibly annoying... |
+1 |
1 similar comment
+1 |
Hey guys, we just deployed a fix for this issue, can you verify if it's working as expected? |
+1 |
@Ghusar Which version is the fix on? Or is this in Postman Canary? |
The fix has been pushed and should be fixed for all existing clients. Closing the issue for now, feel free to reopen it if it is not. |
We are experiencing exactly this issue with Postman v7.0.7 when working with different workspaces. Order changes when merging fork back to master. Newly added tests don't keep their order but end up at the end of the folder. |
Hi @Diaidis , |
@Diaidis we have zeroed in on a possible cause for the issue, will update the thread once the fix has been deployed. |
Hi!
Thank you, guys! Appreciate a lot!
|
+1 |
@ankitjaggi @Ghusar just received another report of this on 7.20.1. Let me know where you'd like logs, etc, shared. |
+1 happens to me a lot, is very time consuming to fix |
+1 |
+1 - happened to me a few days ago. I'm on v7.28.0 |
Is this still an issue for folks using the latest version? |
This should now be resolved. Closing this out as there are no current issues confirmed. |
Hello, I have Postman v7.35.0. Thank you! |
We have this open issue that we're tracking from the recent 7.35.0 version. |
To Reproduce:
Steps to reproduce the behavior:
I expected that order of requests inside a specific folder will not change after merge (there were any changes in orders of requests in changes). But the order of some requests has been changed randomly (only in the context of a single folder. Order of folders left ok).
It`s problematic when the order of requests make difference in the tests results.
Postman desktop version: v6.7.1
OS: Windows 10 (but merge has been done using postman web app)
Additional info:
There is a way to fix the issue by merging the fork 2 times. But after 1 merge you mustn`t remove your collection. After the second merge of the same fork to the base collection, the order issue is fixed.
The problem exists also with pull, but I was not able to do pull twice. So after first pull, the requests have been re-ordered, but the second pull is not possible. So finally the merge to the base collection would change the order permanently.
The text was updated successfully, but these errors were encountered: