Remember environment in History (feature request)

[stantond]

In trying to solve an issue where we need to look back and check which environment a call was made to, we've realised we can't do this in Postman, despite the History feature tracking each request.

Can History be made to remember which environment was used to send a request? I'm not sure if this would be better as a simple reference or a snapshot of the environment variables at that time. Either would have helped us, but I suspect the latter would help more users.

[sdnts]

Hi @stantond, thanks for the feature request! This is interesting to think about. I do not think automatically switching the environment is a good idea, as that might have unintended side effects. We will take a deeper look at this!

[MichelChouinard]

Maybe simply record the request as it was sent, wit all variables decoded, could do the trick?

[vkaegis]

@MichelChouinard With team workspaces now having a shared history, that would be a huge security concern for a lot of our users. We're thinking of a more blunt approach to solving your use case. For example, would just appending the environment name to the URL in the name of the history request provide value?

[JeffreyMercado]

Just going to throw in my 2cents but could this also include collection the request was in as well?

The request history shows the url of the request as typed, but makes it rather useless if it includes variables, especially if different collections share many common variable names. e.g., {{base-url}}/api/... Maybe expand some variables or at least indicate what environment and collection it was run under?

Many requests are also made under certain collections that have pre-request scripts or other inherited properties that gets lost in the history. Would be nice if the history could completely recreate the request as made when selected. i.e., run as if it was in a folder in a collection, and suggest an environment (if not select automatically).