![]() ![]() If I have released, do I need to know that I have 17 builds between start and release? Do I need to keep the knowledge of a bug being found in build 1, fixed in 2, found again in 7, fixed again 9? Or is Found in release 1.0.0 fixed in release 1.0.1 good enough? I'm sure you could probably accomplish a merge action in Bugzilla with some scripting and time, the question is: when is it OK to merge several older versions together? So we still have a list of many many versions. ![]() We have used Archive, but have avoided Merge due to the lack of the undo. Merge versions (rolls several versions together into a new version - no undo) Archive versions (greyed out from pick list)Ģ. Jira does allow us to control the list in two waysġ. Each version is stored in JIRA and issues have an affects version and fixed-in version field that's a multi select.Īfter a short while we have many versions. buildNo is the SVN head revision # at time of build. How are versions related to milestones in a project plan? Who uses versions and how do they use them? I think it is a question of requirements and how are versions used rather than any one tool. We are using jira and still have this problem. It seems that cloning the bug for each version is a good way to track, thus the target version is always tracked in the milestone as well as the fixed version, and the buggy version is always the native version.Īlso to have each clone block the original bug make it a good way to trace the history back to the original submission.Īlthough I have accepted the answer I still welcome your input. What are the best practices around linking versions and bug tracking ? How do you keep track of these versions (found, planned and multiple fixed) in Bugzilla? This is where I need your collective wisdom : this can actually be multiple numbers where we did a retroactive fix for some of these customers (this happens VERY often). The version in which the bug was found (version), the version in which we plan to fix (milestone) the bug and the version in which it has ultimately been fixed (open to suggestions). Lastly, for various reasons, we want to track three different version information : ![]() The end result is that the version combo box is ludicrously long. To make matters worse, because of contractual limitations it is not always possible to upgrade the clients to the latest and greatest, so we must branch, fix, test and release, on the version they currently have, yielding yet another version number. Mix in the fact that our versioning management has been through a few iterations it generated a lot of different versions in the wild. We have a legacy application that has been around for a long time. Bugzilla has customization options that make it easily adaptable to multiple situations.We are in the process of migrating our bug tracking to Bugzilla from a really old version of track and I am running out of Advil. The system also promotes accountability, which is an important factor in improved productivity at an individual level. With Bugzilla, software developers and coders find it easy to meet or even exceed customer expectations. But once installed, Bugzilla is a very capable platform and has the tools to help you do everything you need to keep your bugs tracked and your developers happy.Īmong the benefits Bugzilla brings to the table include enhanced communication among and between software developers as well as improved productivity that results to positive impacts on the product’s quality. The only drawback that many people complain about Bugzilla is that non-Linux/UNIX administrators find it hard and confusing to install and run the software on their system. The system achieves this via a user-friendly Web interface that can be accessed from any modern browser.įeatures that make Bugzilla a standout among its competition include a very powerful Advanced search tool, email notifications, time tracking, reporting and charting, and a request system to mention a few. Bugzilla easily addresses the singular problem of tracking bugs for bugs and defects in software. Bugzilla is an effective bug tracking solution used by many companies and individual developers.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |