Worklog Reports are all based on the same mechanism of aggregation. You will have to defined :
Different views are predefined :
Each report is built with a filtered list of Worklogs.
Criteria | Type | Description |
---|---|---|
Start Date | Absolute or Relative Date | Filtered Worklog have to be equal or after this date (1) |
End Date | Absolute or Relative Date | Filtered Worklog have to be equal or before this date (1) |
Category | Integer | Project Category Id. to use in filtering (2) |
Project | Integer | Project Id. to use in filtering (2) |
Developer | User or Group Name | Developer (Worker or author) having entered the Worklog (2)(3) |
Since Minyaa 3.3.2, the Worklog are now also filtered depending on permissions
|
Date criteria may be filled with a relative Date format. The format follows below codification :
Code | Value Description |
---|---|
NOW | Today (Current Date and Time) |
DATE | Date passed in parameter |
BOW | Begin Of Week |
EOW | End Of Week |
BOM | Begin Of Month |
EOM | End Of Month |
BOQ | Begin Of Quarter |
EOQ | End Of Quarter |
BOS | Begin Of Semester |
EOS | End Of Semester |
BOY | Begin Of Year |
EOY | End Of Year |
+1D | Day |
+1B | Business Day |
+1W | Week |
+1M | Month |
+1Q | Quarter |
+1S | Semester |
+1Y | Year |
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 Operation | Description |
---|---|
BOW | 1st day of current week |
BOW+3D | Thursday of current week |
BOW(+3D) | 1st day of the week of (Today + 3 Days) |
NOW | Today |
NOW+2D | Today + 2 days. Can also defined "+2D" |
+3B | Today + 3 Business Days (Saturday and Sunday are ignored) |
+15D+0B | Today + 15 Days and the date is aligned on next Business Day (if resultant date is not s Business Day) |
+2W-0B | Today + 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 ... |
All provided reports are based on the same aggregation mechanism.
Minyaa provides different Aggregation Criteria (or ReportElement) for most of fields :
Code | Report Element Description |
---|---|
CA | Issue's Category |
PR | Issue's Project |
AS | Issue's Assignee |
RS | Worklog's Author (Human Resource, Worker) |
IS | Any Issue linked to the Worklog |
IS_TS | Issue's Time Spent |
IS_TE | Issue's Time Estimate |
IS_OE | Issue's Time Original Estimate |
IS_R | Issue's Reporter |
IS_Cx | Create Date Supported code are :
|
IS_Ux | Update Date Supported code are :
|
IS_Dx | Due Date Supported code are :
|
ST, STo | Sub-Task linked to the Worklog |
PIS | Only Parent Issue linked to the Worklog |
CP | Issue's Component |
IV | Impacted Version |
FV | Fix Version |
IT | Issue's Type |
PT | Issue's Priority |
RL | Issue's Resolution |
Wx | Worklog Details Supported code are :
|
customfield_999999 | Any custom field identified by its Id |
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 |
On this page: |
See also ... |