Overview

Worklog Reports are all based on the same mechanism of aggregation. You will have to defined :

  • the Report Type (List of Aggregation Criteria)
  • the Criteria to use to filter Worklogs
    Note that filtering will be applied only the filter Criteria is also an Aggregation Criteria
  • and which view to use


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 displayed 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.
CriteriaTypeDescription
Start DateAbsolute or Relative DateFiltered Worklog have to be equal or after this date (1)
End DateAbsolute or Relative DateFiltered Worklog have to be equal or before this date (1)
CategoryIntegerProject Category Id. to use in filtering (2)
ProjectIntegerProject Id. to use in filtering (2)
DeveloperUser or Group NameDeveloper (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.


Since Minyaa 3.3.2, the Worklog are now also filtered depending on permissions
  • Is the current user allowed to browse the Project (BROWSE_PROJECT Permission)
  • Is the current user allowed to browse the Issue (Issue Securities levels)
  • Is the current user allowed to browse the Worklog (BROWSE_WORKLOGS Permission)


Relative Date Operations

Supported Relative Date Operations

Date criteria may be filled with a relative Date format. The format follows below codification :

CodeValue Description
NOWToday (Current Date and Time)
DATEDate passed in parameter
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

Samples Relative Date Operations

This Relative Date engine is used in different part of Minyaa (Timesheet, Report Configuration), and may evaluated against a passed date or the current date. The supported syntaxes can give following samples :

Sample OperationDescription
BOW1st day of current week
BOW+3DThursday of current week
BOW(+3D)1st day of the week of (Today + 3 Days)
NOWToday
NOW+2DToday + 2 days. Can also defined "+2D"
+3BToday + 3 Business Days (Saturday and Sunday are ignored)
+15D+0BToday + 15 Days and the date is aligned on next Business Day (if resultant date is not s Business Day)
+2W-0BToday + 2 Weeks and the date is aligned on previous Business Day (if resultant date is not s Business Day)
EOY(BOQ(EOM(NOW-12W)+3D)-3Q)This formula executed for March 14' 2013, gives December 31' 2012.

You can mix all these functions if is needed ...


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)
Available Aggregation Criteria are proposed in the Workload Report by Worklog Type report, but can also be manually specified in the URL of the Report.

It is also possible to define/restrict default combination of aggregation (See ).


Which Available Aggregation Criteria ar available

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

IS_Rx

(Since xxxx.1.17)

Resolution Date

Supported code are :
  • IS_RD : by Day
  • IS_RW : by Week
  • IS_RM : by Month
  • IS_RQ : by Quarter
ST, SToSub-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
WxWorklog Details

Supported code are :
  • Worklog Author : see RS
  • Worklog Date :
    • WD : by Day
    • WW : by Week
    • WM : by Month
    • WQ : by Quarter
  • WB : Worklog Comment (Worklog Body)
  • WT : Worklog Type
  • WS : Worklog Status
customfield_999999Any custom field identified by its Id

Supported Customfield types are :

Customfield Types
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



How to resctrict available Combination of Aggregation Criteria

As Administrator, you can limit or extend the default combination of Aggregation Criteria:
  • Go to Minyaa Settings page,
  • Select Settings Tabs for Minyaa Time,
  • You will be able to specify the Aggregation Criteria that will usedd (or extend existing) ...

    View Textarea Setting
Minyaa provides different Aggregation Criteria (or ReportElement) for most of fields :    


On this page:


See also ...