Bugflow received a fresh, new look! We redesigned the brand to better clarify our message with the hard-working developers we strive to support.
We did more than putting a fresh coat of paint on things, we released a few more goodies.
We created a blog where we can share updates as we build Bugflow in public. Read our blog →
Expect more content to be added shortly. We will be diving deep into the open source technologies that power Bugflow, share how we keep our development process efficient, and a lot more!
Another area we wanted to be transparent with is our changelog. As we develop Bugflow in public, we created the Changelog section to highlight all the improvements and features that we continue to ship to Bugflow.
Now that we have a platform to share updates, expect our next focus to be the on-boarding process. With so many tools that we integrate with, we want to make a beautiful experience when getting started.
Can't wait to have the next updates out to you soon!
As we roll out more of our internal applications to use Bugflow, we needed to allow guest reporting. Reducing the amount of steps to get customer feedback into our Gitlab is essential to the success of Bugflow. The .4 release rolled out a few more features that make this a reality.
Whether you want a client to report an issue or an anonymous user of your app, we now support guest reporting. Guest reporting is essential to collecting that valuable customer feedback without giving the burden of requiring an account for a client, customer, or guest.
Oh, and you can disable guest reporting right in your project settings if you don’t need it!
One of the challenges we had with implementing this feature was answering the question “Who does the report come from when it hits your project management platform?” In our case, which user created the issue in Gitlab? What we ended up doing was creating a “Bugflow Bot” that reports anonymous feedback. Don’t worry. We will provide a slick way to create this user through onboarding!
Making efficient reporting possible requires less clicks, and less keyboard strokes. If a QA team member is reporting bugs and they report them to a development team member, they shouldn’t have to select the assignee, milestone, status, or priority every single time. Only when something changes.
We now pre-fill these values with what was initially selected so the user can efficiently report bugs and feedback!
Once we solidified our self-hosted Gitlab, we moved onto Gitlab.com in the cloud. Luckily their APIs are the same so this was a breeze! Bugflow now connects to both self-hosted and cloud hosted Gitlab instances so you can use it on all of your Gitlab based projects!
What we are really focusing on with the Bugflow app is the reduction of friction to report an issue. That means, we are doing everything in our power to make issue reporting as seamless and efficient as possible. Once Bugflow is installed, it should be ready to activate on all sites and apps. The 0.3 release continued to dial in the bug reporting process on the embed script.
We are planning to provide for an efficient amount of tools the user can use to report a bug. By implementing the edit screen below, we can easily scale the amount of tools accessible for the user. We’ve implemented the bug location tool so the user can instantly mark in the screenshot where the bug is located on the screen.
We will be releasing other tools in the next couple releases.
Efficiency in bug/feedback reporting is at the core of what we are trying to accomplish. To make this a reality, we added a quick shortcut to jump right to the mark up screen. All you have to do is hold
ctrl + shift + b on both Windows and OSX and you will get right to the recording screen to record your bug!
A screenshot only shows so much. Sometimes there are console errors, design files, descriptions, etc. that should be attached to a bug. We allow the user to upload files to attach to their bug. They will be sent along with the issue to the project management platform you have connected!
When planning a project, we make heavy use of Gitlab milestones. A lot of other project managers do as well. With that being said, we figured it’d be important to select the milestone bound to the current project the developer is fixing bugs for. We pull in the milestones automatically so as an authenticated user, you can select the milestone when you report a bug. We will continue to support this for every project management tool that supports a “milestone-like” functionality.
Labels help to ensure the project’s issues stay organized and the project manager can see right where everything is at quickly. We tend to use labels such as “Blocked”, “Waiting on More Input”, etc. to help organize our project. In the .3 release of Bugflow we now support tagging a bug with as many labels as necessary to ensure the efficiency of your workflow.
We’ve also fixed a variety of bugs, most of those which were recorded with Bugflow. It’s great to use the product to build the product!
Esccancels a reporting of a bug.