Reordering examples

[grinderX19]

It would be quite convenient if there was an ability to rename and reorder saved sample responses.

[aubm]

+1 it would be nice indeed :)

[bhawna2109]

@grinderX19 @aubm renaming saved responses is supported now (using examples) - http://blog.getpostman.com/2017/05/17/mock-responses-in-postman-by-using-examples/

We're working on supporting reordering too - will keep this thread updated once we have a build out.

[Robinnnnn]

+1 would love this feature!

[allwynmendes]

OMG, I am dying for the reordering feature. I guess its possible if we export the collecting and manually move stuff about but that's so Von Neumann. It looks like its been quiet a while since this feature has been requested, or am I missing something ?
BTW Postman Team, thanks for this awesome tool...looking forward to this new feature.

Thanks

[alexprest]

+1 it would be very useful indeed

[dave421]

+1 this would be very nice to have :)

[tonystewart]

+2, any update?

[navid-farjad]

its really needed, i would like to show Correct examples first to use and then listing Wrong request examples. but new its a bit mess in my list, people dont understand it as they see bad example first!

[JeffLoo-ong]

+1 Would love this feature as well <3

[rob7429]

+1 Please implement. I love the tight integration between development and documentation that I felt was sorely missing when using Swagger, but we need control over the ordering of examples to present documentation that makes sense in the face of ongoing changes.

[lenart]

Adding a comment to show my support for this feature. 🙏

[AntonPot]

Yes, please!

[AndrewBoryk]

This would be AMAZING, that way I can make sure all my API docs show the success response first

[fshafiee]

We'd have to clear everything and add examples in the correct order. This is not very productive to be honest and is a feature should have been there from early releases IMO. It gets wors cause I also have an strange issue where sometimes my saved examples go blank when I have them open in a tab. When I switch back to that tab, all of the fields (including name of the example) are empty. Undoing does not help and when I look at the examples list, it is missing. There's something unstable there.

[rcmstark]

Guys, fix this issue ASAP. It's open since 2015!

[happycappie]

@Raja-Simha @Cazaimi can you please provide an update on timeline?

[Raja-Simha]

@conradpronto We are working on fixing the underlying limitation and we expect to release a fix for this by end of November.

[happycappie]

@Raja-Simha @Cazaimi can we still plan for end of November?

[cdolan92]

+1 for this reordering making it into the latest release. Our teams & partners fear the API is broken or somehow not working because random examples, many of them something other than "200 success" are the default...

[markrmoran1]

+1 please - lack of this feature is a real drag guys!!!

[happycappie]

@Raja-Simha can you please provide an update? The last guidance was late September that this would be supported by end of November. And before that it was scheduled to be delivered by mid-June. This is getting silly.

[cdolan92]

I've had to go ahead and delete all non-200/Success examples so that I know our docs show a 200 as the default. Otherwise our documentation defaulted to showing random errors (forbidden, etc)...

[alexprest]

Yeah it's really frustrating and super error prone. Also you might have to do that again in the future because the order might get randomized when new samples are added.

We've been waiting for this fix forever and the age of the threads attests ☹️ @Raja-Simha

[cdolan92]

Right and if it does randomize them in the future, the only option is to procedurally delete and re-add the examples to keep the right index.

[happycappie]

it's an abomination and frankly unacceptable for a mature platform like Postman

[cdolan92]

Is there a public dev timeline that postman publishes? I spent all day learning the new web interface and getting a collection organized to publish, only to find out there are more holes in what I'd consider to be basic functionality (for example, you can't publish API docs with more than 1 environment. This is a big drawback because we support a staging and production URL, see issue #4818).

I ask here because I really love Postman and the Run in Postman feature of the API Documentation is huge... but basic features going unaddressed for 2+ years has me really disheartened, and makes me fear that this may not be the right platform for the long run.

[camellia]

+1

[applebya-wgu]

+1

[wgu-jesse-stewart]

+1

[gerhardvr-finclude]

The ordering of examples is crucial and basic. We typically save examples of valid responses and also invalid responses. Not being able to order them means that more often than not, invalid responses are showed first in the documentation which is VERY confusing.

[cdolan92]

@gerhardvr-finclude and your only option to fix this is to go and manually delete/recreate the responses in the order you want for every endpoint!

[gerhardvr-finclude]

@gerhardvr-finclude and your only option to fix this is to go and manually delete/recreate the responses in the order you want for every endpoint!

Unfortunately it is not even that "simple". I did this to test the viability of the approach. A bit later I updated the name of my collection just to have the examples be randomised one again. Back to square one!

[ethangrinnell78]

How about a cheap hack to bypass the underlying architectural limitation. The UI and documentation would sort the examples in order according to the response header's "date" attribute, regardless of the order in the internal data files. This gives us an attribute that we can edit in the JSON export to force the examples into a certain order, and it is also an attribute that is probably already in the correct order to begin with. I often start with the expected cases before moving to error cases, so earlier timestamps come first. Since this is a change it should have a flag to enable, and it should default to disabled to leave the current behavior.

[juhasev]

@ethangrinnell78 How about postman finally just fix this issue by enabled reordering of responses or at least show the 200 responses automatically as first.

[ethangrinnell78]

There are probably a bunch of ways that seem relatively straight forward. It doesn't need to be a perfect solution for now. But the current method seems pretty broken at random times.

[pjhoberman]

+1 and following.

[jibiabraham]

We're happy to announce that this feature is now available on the latest build of Postman (v8.2.0). You can try it out by either upgrading to this version, or by logging in to postman.com/home on your browser.

[darrylhopkins]

We're happy to announce that this feature is now available on the latest build of Postman (v8.2.0). You can try it out by either upgrading to this version, or by logging in to postman.com/home on your browser.

Thank you so much! I just re-ordered all the examples in my project and it was so satisfying :)