jira
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
jira [2015/09/15 15:48] – [Velocity chart] skip | jira [2020/12/27 20:35] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ===== Atlassian Jira ====== | ||
+ | BugTracker whith a first class Scrum support. | ||
+ | |||
+ | |||
+ | ===== Reports ===== | ||
+ | |||
+ | ==== Single Level Group By Report ==== | ||
+ | |||
+ | Details: https:// | ||
+ | |||
+ | Issues from Filter grouped by some field, like author, status etc. | ||
+ | Nice to track the progress inside some Epic, or inside any other gorup. | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | ==== Control chart ==== | ||
+ | Details: | ||
+ | |||
+ | |Cycle Time| vergangene Zeit zwischen **Work in Progress** und **Work Done** | | ||
+ | |Rolling Average| Mittlere **Cycle Time** 4 Issues vor und 4 Issues nach dem aktuell ausgewähltem. | | ||
+ | |Standard deviation (blue area) | Standard Abweichung der **Cycle Time** von **Rolling Average** | | ||
+ | |Dots on Chart|Issues. X-Achse Position enspricht der Zeit, als das Issue die letzte Swimlane-Spalte erreicht hat| | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | ==== Cumulative Flow Chart ==== | ||
+ | |||
+ | Details: https:// | ||
+ | |||
+ | Different states over time. | ||
+ | |||
+ | There is no easy way to limit the chart to Issues in a specific Sprint - only by creating a special filter. | ||
+ | Those this chart shows all Issues in backlog. This makes it useless. | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | ==== Epic Report ==== | ||
+ | Details: https:// | ||
+ | |||
+ | Story point completed over the time. in a special Epic. | ||
+ | For this report to make sence the Issues in an epic must have been rated with story points. | ||
+ | |||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | |||
+ | |||
+ | |||
+ | ==== Epic Burndown, Release Burndown ==== | ||
+ | Details: https:// | ||
+ | |||
+ | Automatic estimate, about the necessary amount of sprints for he rest of the issues, to complete the | ||
+ | * Release | ||
+ | * Epic | ||
+ | |||
+ | |||
+ | For these reports to make sence the Issues in an epic must have been rated with story points. | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | ==== Velocity chart ==== | ||
+ | |||
+ | how many Story Points have we planed before Sprint start vs. | ||
+ | how many Story Points did we complete? | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | ==== Burndown-Diagramm ==== | ||
+ | |||
+ | The grey Line is the perfect velocity line, which needs to be followed, to successfuly complete the SPrint goal. (complete all issues) | ||
+ | |||
+ | This helps to see, whether the team has enough speed to complete the Sprint. | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | ==== Sprint Report ==== | ||
+ | The list of completed issues per Sprint. | ||
+ | Completed StoryPoints etc. | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | |||
+ | ==== Calculated Custom Fields | ||
+ | Jira can use a plugin "" | ||
+ | https:// | ||
+ | |||
+ | The formula is stored in the describtion of the custom field. | ||
+ | Here an example which uses fields " | ||
+ | |||
+ | < | ||
+ | Nicht verfügbarkeit des Systems | ||
+ | <!-- @@Formula: | ||
+ | log.error(" | ||
+ | log.error(" | ||
+ | |||
+ | | ||
+ | int downtime=((issue.get(" | ||
+ | |||
+ | return downtime+" | ||
+ | --> | ||
+ | </ | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||