Stash orders open pull requests with the least recently modified pull request at the top. This ordering is applied to encourage actioning the oldest pull requests. Each open pull request has a performance impact on the system, so the best workflow is to address and close your pull requests as quickly as possible.
We have an open feature request, STASH-3004, that you can vote for to add sortable columns.
The order is randomly changes every time, so you have to read the whole list again and again each time you open it, just to find something. I don't even start talking about filter, which is also an issue. This is so basic features, that just should there from beginning, and now it is a pain to use it :(
The order does not "randomly" change. The order is updated as the pull requests are updated, with the most recently updated pull request at the bottom and the least recently updated pull request at the top. Pull requests are considered "updated" when new commits are pushed to the branch being merged.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot