Editted: Great! Ronald points out that the deeplinks are available. And it works fine. But since sprintr hides those url's, most people are not aware of this feature, neither are browsers. So this make me redefine this idea to a left-over: Show the deeplinks available on sprintr.mendix.com
All of us developers/PO's/testers are several times a day waiting on https://sprintr.home.mendix.com/ to load, just to be able to go where we want to go. It is a useless step in between getting to our destination which can be a story, an environment, a log or another functionality offered by sprintr. We can arrive to our goal quicker if deeplinks are available:
These deeplinks are available but not many people know them, not even the browsers, so you would have to remember them or store them in bookmarks.
Combined with one's browser's history, this would speed up lots of processes, like refinements for example. And reduce sprintr-traffic by the way.
If browser and users are aware of them, they can and will use them far more often then currently.
So the left-over idea is:
Show the deeplinks available on sprintr.mendix.com
Gentlement… You have just saved me 9 whole seconds (yup I timed it) and a lot of frustration every time I try to access our App’s environments. Thank you 𝔗𝔦𝔪 𝔳𝔞𝔫 𝔖𝔱𝔢𝔢𝔫𝔟𝔢𝔯𝔤𝔢𝔫… Thank you Ronald Catersels :D
I agree with 𝔗𝔦𝔪 𝔳𝔞𝔫 𝔖𝔱𝔢𝔢𝔫𝔟𝔢𝔯𝔤𝔢𝔫 because YES I did not think about researching this in the documentation, and so I remained unaware of it.
I think they already exists. See documentation here: https://docs.mendix.com/developerportal/settings/manage-deeplinks#3-creating-a-developer-portal-deep-link