ReadyAPI 3.7.0 setting up endpoints/environments

[khanchett]

Before ReadyAPI 3.6.0 the setting up endpoints and environments worked really well with importing endpoint information automatically ( I'm using 3.7.0 and was hoping this was updated).  Now if I create a STAGE environment, I cannot just automatically pull in the API's endpoints and if I go into the endpoints I cannot assign an environment. See screenshot:

What I end up having to do is go back and forth and copy/paste the data that I haven't had to for years of usage of ReadyAPI up to this point.  What used to take second takes about 5min each time, and I have to do this a lot.  I'm curious why this was changed to be more cumbersome.  

I've come to the conclusion that it is one of these things:

1. This has other uses that I'm not aware of and that this is a feature and not a bug.  If so I'd like to know how to use it properly

2. This is a bug and needs to be reported.

I'm not sure if anyone else is having this problem or if I'm just way out in left field and missing something simple.  If someone could reply with a fix/workaround to improve this like it was I would be very greatful.

Thank you all!

KHanchett

[nmrao]

Here is the release notes of 3.7.0 to check if that is a feature or not
https://support.smartbear.com/readyapi/docs/general-info/whats-new.html

If you don't find the information, feel free to open support ticket.

Is it possible to use the old version meanwhile?

[khanchett]

This was existing functionality that changed.  I was making sure I was using it right.

I will go ahead and setup a support ticket. 

Thanks

[nmrao]

Sure, it is your call.
By the way, I am a member like you.

[khanchett]

I understand, just going through the process before submitting a ticket.  😉

I gave full details of what I did before and what I see to do now.  I will post here what they tell me and let others know.

Thanks!

[JPP_VF]

Hi,
I'm using the 3.7.0 too, and all seems fine here:

Edit: I think I understood what you did: you want to update an existing endpoint, by changing its Environment. Right? In this case, I have the same behavior. Workaround is to create a new one with the right Environment...