Versions Compared

Old Version 8

changes.mady.by.user Praveena Manohar

Saved on

compared with

New Version Current

changes.mady.by.user Cristian Oancea

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Info

Rich Filters::Time Tracking Dashboards is an extension of the Rich Filters for Jira Dashboards app. 

When Rich Filters::Time Tracking Dashboards is installed, a new field called rfWorklog is automatically added. The field can be used to perform work log queries via JQL. When used in rich filters and rich filter gadgets, the work log queries can filter and group the issues and their work logs. This mechanism is used by the Rich Filter Controller gadgets to provide dynamic filters on worklogs and by the other rich filter statistics and chart gadgets to generate links to the issue navigator. Check the key concepts page to learn how dynamic filtering and grouping based on work log attributes work.

...

  • when used to aggregate issue values (issue count or issue value fields) or when used in Jira's issue navigator – the query returns all the issues containing at least one work log satisfying the WQL query

  • when used to aggregate worklog values (Worklog Time Spent) – the query returns the work logs (belonging to the returned issues) satisfying the WQL query

Tip

The It is possible to apply worklog queries can be applied to only to some of the issues. For instance, the base JQL query:

priority = Highest OR rfWorklog ~ "dateStarted >= 2018-09-01"

returns:

  • when applied at the issue level: all the issues having either priority Highest or containing work logged after September 1st, 2018

  • when applied at the work log level: all the work logs belonging either to issues having priority Highest or plus the work logs having the Worklog Date after September 1st, 2018

Note

Do not use worklog queries in referenced Jira filters

The ability to filter at the work log level provided by the WQL can work only if the worklog queries are directly available to the app – i.e. if they are used in the “top-level” JQL – as opposed to being used in a separate Jira filter that is referenced in the JQL available to the app. Indeed, when a clause of the type filter = <filter ID> is used in the JQL, the rich filter gadgets can only see which issues are selected by this filter, so any worklog queries present inside it do not have the worklog-level filtering effect.

Note

Jira's native searching based on work log attributes

Jira also provides native support for JQL searches based on work log attributes via the JQL fields worklogAuthor, worklogDate, and worklogComment. This functionality can be used to filter issues, but when used in rich filter gadgets, it does not also filter the work logs of the returned issues. In addition, combining multiple clauses using the native worklog JQL fields can be tricky. We recommend you use only WQL for queries used with rich filter gadgets.

Anchor
section3
section3
3. Worklog filtering in rich filter configurations

...