Worklog Reports - Concepts

How worklogs are displayed

Different views are predefined :

  • hierarchicView : Providing a Hierarchical display of aggregated data with expand and collapse features.
  • flatView : Providing a classical display.
  • excelView : Similar as flatView but without graphical rendering, used to export to Excel (undecorated HTML file).
Using Flat Views, the reports may display Issues with Sub-Tasks.

In such cases, the default behavior of the Flat View is to display the values associated to leaf of the agregation tree, assuming that each parent node is just a calculation of leaf's values.



But, the both (Issues and Sub-Tasks) are able to have logged Work, and then the value displayed in Flat View is only the Sub-Task's Spent Time.

To avoid to display only the Sub-Task's Spent Time and be able to see Issue's Spent Time, a new parameter has been introduced in Reports : the Flattened Level (let me know if you find a best term !).



The Flattened Level expressed the depth of node to flat when displaying the Flat View.

By default, all nodes are flattened. For example, if your report provides an aggregation based on :
  • Category
  • Project
  • Issue
and the display Issues have sub-task, you will be able to force the view to flat node only on the 3 first nodes.



Hopping that this explanation is comprehensive.

How Worklogs are filtered

Each report is built with a filtered list of Worklogs.

The filter is possible with below criteria.
Criteria TypeDescription
Start DateAbsolute or Relative DateFiltered Worklog have to be equal or after this date (1)
End Date Absolute or Relative DateFiltered Worklog have to be equal or before this date (1)
Category IntegerProject Category Id. to use in filtering (2)
Project IntegerProject Id. to use in filtering (2)
DevelopperUser or Group NameDevelopper (Worker or author) having entered the Worklog (2)(3)
(1) Date Criteria support Relative Dates.

(2) At least one of this criteria have to be selected. Selected values have to be valid for Category and Project.

(3) If a Group is specified, the filter will take in account each Group's members.

Relative Date Operator

Date criteria may be filled with a relative Date format. The formay follows below codification :
CodeValue Description
BOWBegin Of Week
EOWEnd Of Week
BOMBegin Of Month
EOMEnd Of Month
BOQBegin Of Quarter
EOQEnd Of Quarter
BOSBegin Of Semester
EOSEnd Of Semester
BOYBegin Of Year
EOYEnd Of Year
+1DDay
+1BBusiness Day
+1WWeek
+1MMonth
+1QQuarter
+1SSemester
+1YYear
The supported syntax allows for example :
  • StartDate = -2W, EndDate = +3D
  • StartDate = BOW-2W, EndDate = EOW
  • StartDate = BOM-2W, EndDate = EOM
Future release should support some syntax like BOM(NOW-2w) for begin of Month relatively to today - 2 Weeks, and so ...

How Worklogs are aggregated

All provided reports are based on the same aggregation mechanism.

Each report performs its aggregation depending on the passed Report Type.

The Report Type may be defined by different ways :
  • Predefined depending on each report and selectable during the Report Configuration,
  • Built using a sequence of Aggregation Criteria (See Workload Report by Worklog Type)
Minyaa provides different Aggregation Criteria (or ReportElement) for most of fields :
CodeReport Element Description
CAIssue's Category
PRIssue's Project
ASIssue's Assignee
RSWorklog's Author (Human Resource, Worker)
ISAny Issue linked to the Worklog
IS_TSIssue's Time Spent
IS_TEIssue's Time Estimate
IS_OEIssue's Time Original Estimate
IS_RIssue's Reporter
IS_CxCreate Date

Supported code are :
  • IS_CD : by Day
  • IS_CW : by Week
  • IS_CM : by Month
  • IS_CQ : by Quarter
IS_UxUpdate Date

Supported code are :
  • IS_UD : by Day
  • IS_UW : by Week
  • IS_UM : by Month
  • IS_UQ : by Quarter
IS_DxDue Date

Supported code are :
  • IS_DD : by Day
  • IS_DW : by Week
  • IS_DM : by Month
  • IS_DQ : by Quarter
STOnly Sub-Task linked to the Worklog
PISOnly Parent Issue linked to the Worklog
CPIssue's Component
IVImpacted Version
FVFix Version
ITIssue's Type
PTIssue's Priority
RLIssue's Resolution
WxWorked Periods

Supported code are :
  • WD : by Day
  • WW : by Week
  • WM : by Month
  • WQ : by Quarter
customfield_999999Any custom field identified by its Id


Supported Customfield types are
Customfield TypesSamples
com.atlassian.jira.issue.customfields.impl.SelectCFType
com.atlassian.jira.issue.customfields.MultipleSettableCustomFieldType
com.atlassian.jira.issue.customfields.MultipleCustomFieldType
com.atlassian.jira.notification.type.UserCFNotificationTypeAware
com.atlassian.jira.issue.customfields.impl.ExternalCFType
com.atlassian.jira.issue.customfields.impl.DateCFType
com.atlassian.jira.issue.customfields.impl.DateTimeCFType
com.atlassian.jira.issue.customfields.impl.AbstractMultiCFType
com.atlassian.jira.issue.customfields.impl.AbstractSingleFieldType
For any other are toString() is assumed