We manage our Jira workflow through Epics.
Because a sub-task is not linked to an Epic we have created a post script to populate a custom text field called “Epic Reporting Name”, with the Epic name against all issues & sub-tasks..etc This is imported into EazyBI as a dimension. In our reports the “Epic Reporting Name” dimension is typically on Pages to allow the user to filter for the Epics they are in charge of.
Problem:
Over time the number of Epics will grow and we don’t want to have the names of the Epics which have been ‘closed’ to appear in the drop-down filter. It creates too much noise for the user. We need some capability to filter out these closed Epics.
Things I’ve tried:
- Added another custom text field, “Epic Status”, containing the ‘closed’ status, again imported as a dimension. I added this dimension to Pages: so we had both “Epic Status” & “Epic Reporting Name” in that order. On Rows I had the Issue dimension.
The issues in the resulting table displayed the correct results and only showed those issues where “Epic Status” <> “Closed”.
However, when I set the “Epic Status” filter = (none), the names of those closed Epics still appeared in the “Epic Reporting Name” filter. So it appears there is no link between the filters & their contents?
- Tried a regular expression on the table column to exclude all issues where “Epic Status” = “Closed”. Which it did correctly. But this also had no impact on the contents of the filter.
So I guess we’re looking for some MDX to create in a calculated member for “Epic Reporting Name” which will create a set based on the value of a custom field in the Issue dimension (whether that value is then brought in a dimension in its own right or not)?
Constraints:
We cannot use JQL to filter out these Epics at the source import because there are finance users who will want to see them in their reports.
Thanks in advance.