Hello Orangescrummers! As per our commitment here we come with our latest product update. However, we have released the Bug & Issue Tracking feature.
Orangescrum is continuously bringing new updates that make it easier for you to manage your projects. We’ve got some major ones for you this time!
We’re always working on new updates to make Orangescrum even more convenient and bring you a great user experience. In our last update, we released the Profitability Report. And this time, we have some major updates for you!
Product Update: Bug & Issue Tracking
A bug is often a piece of code that does not work as expected. It may be that a feature or a specification supposed to enable a certain functionality has been coded incorrectly.
As a software engineer, it is your responsibility to identify and document these bugs so that they can be fixed and quality products can be delivered.
Bug tracking is one of the important aspects of a software development lifecycle to deliver quality products.
So, Having a robust defect management process improves the quality of software, which in turn improves the sustainability of the organization.
It also helps you to stay ahead of your competition, so you can book higher profits.
With Orangescrum Bug & Issue Tracking feature you can add every detail at your ongoing development projects.
To add bug details, just click on Bug Tracking at the left menu at Orangescrum. And click on “Create Bug”.
A Guide to Create a Bug Details in Orangescrum
- Select Project – Select the project from the drop-down where you found the bug.
- Select Task – Select the related task of that project at where you found the bug.
- Bug Name – Name your Bug.
- Select the Bug-type – The founded issue can be a bug, or a required improvement, or might be a query. So add your bug type accordingly.
- Select Bug Severity – Select the Bug Severity.
- Reported by – Select the user who has reported the bug.
- Bug Detection Phase – In case the task is in the development phase or in the designing phase, Add the bug detection phase accordingly.
- Bug Category – Select the Bug Category.
- Select Client – Select if the Client has reported this bug or not.
- The Bug Origin – Put the origin of this bug, as it could be from Designing origin, or Development origin, etc.
- Resolution – Users need to add the required resolution for the bug.
- Bug Owner – You can select a user as bug owner where the selected user is able to monitor all bug handling activities.
- Due Date – Add the estimated due date to resolve the bug issue.
- Environment – Select the bug environment like operating system, browser, device, etc.
- Impacted Area – Add the details where the found bug has made the maximum impact.
- Description – Add the detailed bug information to the description field.
- Attachment – Add the bug-related attachments.
The Bug List Page:
Here the user can able to find the Detected Bug List as it shows bug name, Issue type, the bug severity, and the Status (Closed, In-Progress or Yet to start).
So the user would have a clear view of bug status for all projects with a single dashboard.
Read Full Blog at Product Update: Bug & Issue Tracking - Orangescrum Blog
