개관

벌레 대쉬보드

당신의 발달의 건강에 당신의 전망

확대하기 위하여 누르십시오

"고전적인" 대쉬보드 전망은 당신의 개발 노력의 국가의 개관을 당신이 제대로 Bugzilla를 사용할 때 당신에게 제공한다. 그것은 정보의 6개 중요한 조각을 당신에게 제공한다:

1. 각 분대 내의 우선권에 의하여 공개된 문제점
2. 문제점에 지정되는 사람 에의한 공개된 문제점
3. 모든 공개된 문제점
4. 당신의 4개 최고 종류의 각각 내의 공개된 문제점
5. 문제점은 과거 7 일 안에 열었다
6. 제품 내의 우선권에 의하여 공개된 문제점

확대하기 위하여 누르십시오

Bugzilla를 이용하는 기업에는 수시로 그들의 창고에 있는 많은 제품이 있을 것이다. 개인 과제, 균형을 잡는 우선권 및 곡예를 하는 책임에 작동하고 있는 동안 큰 그림의 대위를 잃지 않는 것이 중요하다. 벌레 대쉬보드는 당신의 프로젝트의 각각을 건강 상태의 at-a-glance 전망을 제공한다. 우리는 당신이 만큼 불쾌한 놀람을 미워한다!

당신은 많은 수를 보고하는 우선권 1를 위해 대쉬보드에 온도계를 볼지도 모르고다 관지하 된다. 아래에서 설명한 바와같이 온도계는, 골재의이다 모두 저 우선권 내의 문제점. 당신이 전면으로 염려해 되기 전에, 그 문제점을 당신이 in. 관심이 끌리는 제품에 할당되어 찾아내기 위하여 Priority Within 제품 (우선권 구조)에 의하여 문제점을 이용하십시오.

책임

확대하기 위하여 누르십시오

A balanced workload is important, not just for the health of the individual members of your development team, but for the health of the projects. The Bugs Dashboard helps you manage the workloads of individuals by providing a view into their assigned responsibilities within the repository.

The numbers at-a-glance for individuals, however, must be tempered with knowledge for the project. For example, someone may be able to dust off a large number of small nuisances in short order while another individual requires time to work through a complex issue. The numbers themselves are not fool-proof, but they are an excellent starting point for identifying potential problems.

The numbers can help you avoid bottlenecks and balance the work amongst the development team members. Perhaps most importantly, the visibility the Bugs Dashboard brings about can generate communication and discussion which can lead to improvements in all areas of development.

Thermometers

Click to enlarge

There are five thermometers on the dashboard; a total of all open issues and the first four individual categories. Because not all categories may be reported (.e.g Priority 5 and lower), you may not be able to sum the four individual categories to equal the total thermometer. The total open issues is a general statement about the health of your development. However, there are two schools of thought: a lower number could represent a lack of quality testing procedures whereas the other school says too large a number represents a poor quality of development.

Each situation is different and you must determine which statement applies to your situation. If you have a very complex system, a large number of open issues early in the cycle may very well be acceptable. As the release date approaches, you probably want to focus on the Priority 1 Thermometer more so than the others as you drive for a quality release.

Your Priorities - You Can Have It Your Way

Overview

Click to enlarge

When someone opens a new issue, they're allowed to define a priority. If the issue is opened by a Quality Assurance Engineer, it may well carry an initial priority that would be different if you opened it. When you "Set Priorities", you're telling the development team what you want them to focus on. This allows you to focus resources on issues that provide the greatest benefit to your expectations.

One thought is that you ask everyone who opens a new issue to classify it using a very low classification or you establish a classification that is "to be prioritized". If you elect to use this strategy, we strongly recommend that you provide a mechanism for everyone to notify of expections - those issues that require your immediate attention. You don't want to wait a week, if that's your normal schedule, to prioritize a critical issue. For this reason, we do not recommend this strategy.

Changing a Priority

Click to enlarge

To adjust the priority of an issue, click anywhere on the issue where you see the cursor change to four arrows.

Click to enlarge

Hold the mouse down and drag the issue into the priority box of the priority you wish to set it to. Note: if the priority you wish to set the issue to is higher or lower than is visible on the screen (requiring scrolling), use the mouse wheel to scroll while holding down on the issue.After you release your mouse and the issue appears in the list of priorities you want it moved to, you must enter a comment and submit your change. This can be done for every change or once after you've set all your priorities. The determining factor of when you submit should be what you want as the comment on the issue(s) you're submitting. For example, there's only one classification for "Priority 1". If you have a dozen priority one's - all of which are critical, which should the development team focus on first? You may use the comments to communicate your desires to the development team.

Your Severities - How Badly Does It Affect You?

Overview

Click to enlarge

As mentioned above, there's only one category of "Priority 1" no matter how many issues are in that category. Once you have many issues categorized as priority ones, you're faced with the delima of how to address them. The Bugs Dashboard helps you through this by allowing you to see the big picture as you work to put order to each of your priorities.

The "Set Severities" page assists with the proper classification of each issue. By looking at the big picture, you can quickly work through the questions that surround each issue. Once this is completed, you may return to your priorities and work on those top level priorities with the most severe impact.

Changing a Severity

Click to enlarge

You do the same thing for Severities as you did for "Changing a Priority" above. Recall that when you have set a severity, you need to determine whether a single comment works for all severities (e.g. "Severity set by Project Stakeholders on 28 Feb 2007") or individual comments are necessary. This is the same as it was for commenting on a priority.

How to Keep Issues from Causing You to Age Too Quickly!

Click to enlarge

As you work through your issues over time, you may find issues of a lower priority sliding further and further out. The Bugs Dashboard works hard to keep these from falling "out of sight, out of mind."

You define the initial age at which you wish to report in the preferences (property files). By default, the process looks for issues 30-days and older. However, you may wish to look at those between the 7-day period on the dashboard and the 30-days of the aging page (or focus only on those more than 90 days out). The Bugs Dashboard provides you with the ability to specify the number of days to being the aging process from.

Your Dashboard - Your Way!

Create Your Own Widgets And Add Them To A Portal

Click to enlarge

Bugs Dashboard now offers two views: Classic and Portal. The Classic view offers the five default metrics in a fixed format. The Portal view offers you the ability to register your creations and view your metrics your way!

The Portal view offers the same five default metrics, but you control if and where they appear. These "portlets" act as individual windows within the page. You can drag-and-drop them to change their position. You can control their appearance through a configuration file. Likewise, you can add your own creations to the Portal.

You may have need for information from your Bugzilla repository which is not currently offered through the Bugs Dashboard. For example, tracking milestones or hours, projecting releases, or forecasting may be desirable, but unique to your situation. Now, you can create your own server-side objects which return a string of HTML and then plug it into the Portal as your own portlet. You can even provide your own stylesheet!

The Developer edition allows you to create one portal with any number of portlets. The Enterprise edition allows you to create any number of portals which are then added to your menu bar with your style and your definition of portlets. This allows an enterprise to track multiple projects separately (e.g. use different portals with portlets selecting specifics for that project). The project details (i.e. portal) can be projected on a wall for all to follow or individual project managers can follow the details that are pertinent to them with greater ease.

When You Just Have to Have More

When properly configured with the URL to your issue tracking system, the Bugs Dashboard allows you to drill down into each issue. You may however, be required to login when you drill down as the Bugs Dashboard has no means of exchanging logins with the issue tracking system. We recommend a read-only account for customers and stakeholders to have visibility into issues as this can help them set the proper priority and severity for an issue without accidentally modifying the issue itself.