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 of the week comes from Dominik Roszkowski, who asked about the possibility of seeing the test results of the Flutter tests step in our Test Reports extension.
Our next feature request comes from Hisham Bakr, who would like to see a PagerDuty integration in Bitrise. Utilizing PagerDuty can help developers keep track of their app health, and through the integration, users would be able to create Slack alerts for tests, for example.
Next up, we have a feature request from Vladimir Ivanov about separately managing which apps to receive notifications from. We have a Watch feature that may be the exact thing needed here — if this isn’t what you were looking for, Vladimir, please let us know, and we’ll look into it!
Next, we have a request from Gaurav Sharma, who would like to see the ability of adding, modifying, and deleting secret environment variables from an app directly using APIs. Having this option would open up new possibilities for users in pushing builds to the App Store/Play Store, and would, in certain cases with a high number of apps involved, make it easier for them to manage secret env vars.
We also saw a feature request from Shota Nagahori, who would like to see a separate step that enables users to export the test results to the Test Reports feature, instead of being only able to do so through already supported test steps.
Next, we have a request from Kelvin Tan, who asked about an integration for sending test coverage information to CodeClimate.
Our next feature request comes from Frank Harper. Frank would like to see the option of using a regex for the old_value input in the Change Value step.
Next, we have a feature request from Ushisantoasobu, who would like a feature that would enable him to get continuous feedback on test failure rates.
Next up, we have Stefanos Georgiou's feature request for an additional status under the GET build API, specifically, one that would display the number of builds still in queue.
Our next request comes from Stefan de Vogelaere, who would like to see a section on the Bitrise dashboard dedicated to a list of disabled apps. This would come in handy when having multiple users who aren’t fully aware of the setup going on.
Our next request comes from Magdalena Strzoda, who would like to see the option of adding a step that runs in case a build is aborted, much like the existing option for failed ones.
Last but not least, we have a feature request from Satoshi Nagasaka, who would like to be able to add triggers for pull request description updating. In Satoshi’s case, this is needed since one of his workflows refers to the labels attached for checking whether the pull request is valid.
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!