{"id":4608,"date":"2021-06-11T14:16:15","date_gmt":"2021-06-11T12:16:15","guid":{"rendered":"https:\/\/www.actonic.de\/massgeschneiderte-berichte-in-jira-standard-und-fortgeschrittene-zeiterfassung\/"},"modified":"2023-03-29T10:24:27","modified_gmt":"2023-03-29T08:24:27","slug":"massgeschneiderte-berichte-in-jira-standard-und-fortgeschrittene-zeiterfassung","status":"publish","type":"post","link":"https:\/\/actonic.de\/en\/massgeschneiderte-berichte-in-jira-standard-und-fortgeschrittene-zeiterfassung\/","title":{"rendered":"Custom Reports in Jira"},"content":{"rendered":"

[vc_row][vc_column][heading title=”The default reports in Jira” heading=”h2″ font_weight=”” el_id=”1623413713844-7f2022aa-5853″][vc_column_text]<\/p>\n

Jira offers many ways to track time for processed tickets. These functions are simple to use, but their possibilities are pretty limited. In the next section, you\u2019ll get to know how to use time tracking and how to create reports:<\/p>\n

Therefore, it is important to check, if you have all needed admin rights. Moreover, you have to set up your templates<\/span> for time tracking in a correct way and activate the right authorization types in the menu.<\/p>\n

If you have the correct settings, you can create time reports in Jira. You can create basic reports if you go to the \u2019Reports\u2019 section, click Forecast & management and select \u2019Time Tracking Report\u2019. Then select your preferred settings and click \u2018continue\u2019 and you\u2019ll receive your time report.<\/p>\n

[\/vc_column_text][vc_single_image image=”4601″ img_size=”full” alignment=”center”][\/vc_column][vc_column][\/vc_column][\/vc_row][vc_row][vc_column][heading title=”Basic time tracking in Jira: The disadvantages” heading=”h2″ font_weight=”” el_id=”1623413935991-355242da-c69a”][vc_column_text]<\/p>\n

If you work longer with Jira time tracking, you will notice that this function has limits i<\/span>n its efficiency. The following seven pain points will show you why basic time tracking in Jira is limited:<\/p>\n

    \n
  1. \n

    You can not estimate for which tickets the most time was spent in a specific period of time.<\/p>\n<\/li>\n

  2. \n

    You can not group your time tracking through an epic, label, component or any other Jira field.<\/p>\n<\/li>\n

  3. \n

    You can not determine time for multiple projects of one client.<\/p>\n<\/li>\n

  4. \n

    You can not create reports for specific users, groups or teams.<\/p>\n<\/li>\n

  5. \n

    You can not adjust mistakes based on your time tracking results.<\/p>\n<\/li>\n

  6. \n

    For client projects: You can not compare the hours that are established in the contract and the logged hours a team or user has worked. This could result in a bad controllable budget of your project.<\/p>\n<\/li>\n

  7. \n

    You can not determine the logged time for a specific user for invoicing.<\/p>\n<\/li>\n<\/ol>\n

    [\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][heading title=”Report Builder as an extension of basic Jira time tracking” heading=”h2″ font_weight=”” el_id=”1623413987755-912d6b7f-7708″][vc_column_text]<\/p>\n

    Because of the mentioned reasons, the basic Jira time tracking is helpful but restricted in its functions. A simple and easy way to close this gap is the Jira app Report Builder. This tool allows you to create every Jira report you might ever need, cause it provides two variants of reports for you: report templates and Open Source reports.<\/p>\n

    A report template is a great tool to create reports fast and easily through its predetermined settings. You can create reports like timelines and cake diagrams there. Furthermore, with the Scripted Reports function of Report Builder, you can create different Open Source reports. Here you can configure reports with HTML and JavaScript. Every created report can be exported as CSV or PDF and provided for your supervisor or client. Report Builder is the smart solution for all of the mentioned disadvantages of basic Jira time tracking and a real \u201eall-rounder\u201d in Jira time tracking. <\/span><\/p>\n

    [\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][heading title=”An example: The Scripted report \u201eCreated vs. Resolved\u201c” heading=”h2″ font_weight=”” el_id=”1623414168365-289c84f8-7631″][vc_column_text]<\/p>\n

    The Scripted Report<\/span> \u201eCreated vs. Resolved\u201c is very useful for heads of big teams.<\/span> This report allows you to compare the number of created and resolved tickets for a specific time frame. This empowers the team lead to analyze the workload of a team, user or project and to make decisions based on the won data.<\/p>\n

    Through choosing a specific time frame and a user, team or project as JQL scope a cake or line diagram gets created. These diagrams display the relationship of the created and resolved tickets in a graphical way. This created graphic can be the base of workload analyzes afterwards. <\/span><\/p>\n

    [\/vc_column_text][vc_single_image image=”4603″ img_size=”full” alignment=”center”][vc_column_text]<\/p>\n

    All used parameters can be configured and adjusted individually with HTML and JavaScript.<\/p>\n

    [\/vc_column_text][\/vc_column][\/vc_row][vc_row][vc_column][heading title=”Curious? Let us introduce you to Scripted Reports through our article series Custom Jira Scripts with Report Builder:” heading=”h3″ font_weight=”” el_id=”1623414374941-854ca713-dc47″][vc_empty_space height=”16px”][\/vc_column][\/vc_row][vc_row][vc_column width=”1\/2″][vc_column_text]<\/p>\n