===== Atlassian Jira ======
BugTracker whith a first class Scrum support.


===== Reports =====

==== Single Level Group By Report ====

Details: https://confluence.atlassian.com/jira/single-level-group-by-report-185729552.html

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://confluence.atlassian.com/jira/files/185729552/singlelevelgroup_report-report.png?200}}

==== Control chart ====
Details:https://confluence.atlassian.com/display/AGILE066/Viewing+the+Control+Chart

|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://confluence.atlassian.com/download/attachments/600867587/gh_6-2-1_control-chart.png?200}}


==== Cumulative Flow Chart ====

Details: https://confluence.atlassian.com/display/AGILE063/Viewing+the+Cumulative+Flow+Chart

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://confluence.atlassian.com/download/attachments/600867586/gh_6-2-1_cfd.png?200}}


==== Epic Report ====
Details: https://confluence.atlassian.com/display/AGILE063/Viewing+the+Epic+Report

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://confluence.atlassian.com/download/attachments/600867591/gh_6-2-1_epic-report.png?200}}





==== Epic Burndown, Release Burndown ====
Details: https://confluence.atlassian.com/display/AGILE066/Viewing+the+Epic+Burndown

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://confluence.atlassian.com/download/attachments/720408095/agile-epicburndown-annotated.png?200}}


==== Velocity chart ====

how many Story Points have we planed before Sprint start vs.
how many Story Points did we complete?

{{https://confluence.atlassian.com/download/attachments/600867585/gh_6-2-1_velocity-chart.png?200}}


==== 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://confluence.atlassian.com/download/attachments/720408144/gh_6-2-1_burndown-chart.png?200}}


{{https://confluence.atlassian.com/download/attachments/720408144/gh_6-2-1_burndown-chart.png?200}}


==== Sprint Report ====
The list of completed issues per Sprint.
Completed StoryPoints etc.

{{https://confluence.atlassian.com/download/attachments/720408131/agile-sprintreport.png?200}}



==== Calculated Custom Fields  ====
Jira can use a plugin "" to calculate fields by using another fields.
https://innovalog.atlassian.net/wiki/spaces/JMCF/overview#JIRAMiscCustomFields-calculatednumberfield

The formula is stored in the describtion of the custom field.
Here an example which uses fields "nichtverfuegbarkeitBis" and "nichtverfuegbarVon" to return its difference.

<code>
Nicht verfügbarkeit des Systems
<!-- @@Formula: 
log.error("Value of field nichtverfuegbarkeitBis is: "+issue.get("nichtverfuegbarkeitBis"));
log.error("Value of field nichtverfuegbarVon is: "+issue.get("nichtverfuegbarVon"));
 
  
int downtime=((issue.get("nichtverfuegbarkeitBis").getTime() - issue.get("nichtverfuegbarVon").getTime()) / 1000 / 60) ;

return downtime+" min";
-->
</code>

{{https://i.imgur.com/iUXFjM4.png}}