Developing new features for our platform is one of the key ways we can make sure we are giving you the best service possible — and we wouldn’t be able to do it without your help. Let’s take a look at all the feature requests that we have received in the past few weeks!
Our first feature request comes from Jmunoz, who would like to see extended glob capacity for trigger machines, which would be useful when trying to start builds upon any branch other than master being pushed to version control.
Next up, we have a request from Onyx Mueller, who would like to see the option of being able to choose a default profile when it comes to his Bitrise account.
We also saw another request from Jmunoz, this time, about being able to execute chained workflows conditionally, based on an environment variable’s value.
Jmunoz also posted a feature request about the option of Bitbucket selective builds being supported, which would be useful in the same use case scenario as the "Execute chained workflow conditionally" request.
We also saw a feature request from Driesrentio, who would love to see some quick action buttons next to each build on the builds page.
Our next one comes from Luke S, who was asking for the option of being able to download the .bitrise.secrets.yml file from a workflow’s secrets page, in case someone needs it their local Bitrise CLI.
Next, we have a request from Bofei Zhu, who suggested adding a menu in the organization/personal settings that lists stacks for every app, allowing users to make multiple changes in one place.
Our next one comes from Rick Manelius, who would like to see the inclusion of commit hashes for manual builds. This would mean that users don’t have to bother with manually copying the hashes over to the commit messages fields for each build.
Lukas Kurucz also posted a request about seeing the option of continuous, interactive Slack notification updates about a build’s progress and status.
Next up, we have another suggestion from Luke S, who would like to see some hints and/or error text added when renaming a workflow in the workflow editor, particularly when there is some problem with saving the name change.
Our next one is another request from Jason, this time, about having a “limited builder” role, which essentially would be used as a developer role, but with limitations as to which builds it can manually start.
Jason also submitted one about the possibility of a notification/monitoring dashboard to see historically how often a build was on-hold, which would help with deciding whether a user needs more concurrencies.
Next up is Tdekoning with a request for support for dynamic feature modules when it comes to UI testing. This would be handy when working on apps that consist of dynamic features, and that, at the same time, has UI tests.
Our next request comes from Jasmin Abou Aldan, who would like to see the option of staying in the same browser window while opening up a workflow. This would make handling maintenance and updates for multiple projects in parallel easier, for example.
Next up is Katial with a request for updating the SDK versions on LTS Stack. Due to the current versions not being present, Katial was having trouble with creating an emulator with the latest API.
Our very last feature request comes from Artyom Ok, and is about having the option of making steps optional when it comes to build pass criteria.
That’s it for now, folks! Make sure you go and vote on your favorite feature requests to help us see just what it is you'd really want to see on Bitrise. Have any ideas that you haven't seen mentioned? Post them on the feature request page — all you have to do is log into your account, click "New Topic" on the top right corner of the page, and you're good to go! See you in two weeks with a new Feature Request Friday!