After JIRA is installed, you can create several tasks and view them several times using filters. This is not intuitive. Therefore, you can find a graphical plug-in on the Jira website. See the following link for details: http://www.atlassian.com/software/jira/plugins/charting.jsp
Use and Installation
-
- Copy the plug-in jar to JiraWebApplication WEB-INF/libDirectoryAnd then restart Jira..
Note: 1) You must restart Jira before proceeding to the next step.
2) these three fields must be added according to their own Custom Field Types (do not use Date Picker to add them) (that is, do not add Date Picker and then name it resolution date, etc, although the searcher of resolution date is still of date pick)
- Administration> Issue field> Custom Field Add a new custom resolution Date Field. Do not add it to any workflow transition screens (such as resolve screen ), but if you want it, you can display it on the default screen ("problem navigation bar.Suggestions: The name of the Custom field is "Resolution date ". Warning set searcher to "Date Picker" correctly (Benefit: You can search and filter by date resolved)
-
- Administration> Add a new date of first response type custom field. Do not add it to any (Transition) screens. Warning set searcher to "Date Picker" correctly (Benefit: You can search and filter by date of the first comment !) <This value determines the time of the first comment as the time of the first response. The value is not updated when I add comment in my trial administration.>
-
- Administration> Add a new custom field of time in status type. do not add him to any (Transition) screens. warning set searcher to "free text searcher" correctly (Note: Do not expect it to be displayed in any screens, It is not stored in human readable form)
-
- Administration> indexing re-Index
after installation, everyone can set the dashboard and set the graphical Portlet on Their Own Dashboard, preferably with the filter.
Project Description:
- recently created issues -shows the diagram of the recently created issue. If the number is large, the developer must fix the issue immediately.
- created vs resolved issues -trend chart of newly created and resolved issue. At the beginning of the test, many bugs were found, but few bugs were solved. At the end of the test, only a few bugs were found and many bugs were solved. The software quality can be determined based on this trend.
- resolution time -average time for solving issue. We can see that the efficiency and speed of the team should be improved as soon as possible to solve the problem and reduce the time, many companies have stipulated that they can use filter and resolution time to check if the problem is solved within 24 hours.
- average-age open issues -displays the histogram of the average number of days when the problem is not resolved. This chart shows the average time left over from a specified period of time (for example, daily or weekly.
- pie chart -displays the problem pie chart from the project or filter summarized by statistical type. The problem can be summarized by any of its statistical attributes (such as the State priority ).
- average time in status -displays the average number of days of a problem in one status.
- Average number of times in status -displays the average number of times the problem (all resolved) has a status.
- time to first response -number of hours for the first issue response in the project or filter.
- time since chart -displays the number of all issue in a given time field. For the Date Field, select create date, update date, due date, resolution date, date of first response. Selecting different date fields overlaps with the previous ones, which is more flexible.
To sum up,
The first is to check the quantity, the number of new bugs, the number of bugs to be solved, and the number of each status to determine the development trend of product quality.
The second is to look at the time, the average time of bug handling, and the speed and efficiency of the team.
Another article of JiraArticle
Basic configurations and settings of Jira
