Show in report only issues, created after specific date

[Anton_Kruglikov]

Hello,

How can I show in report only issues, created after specific date?

For example, in table I have 10 issues, created on different dates (on December, January, February). But I want to work with issues, created after February, 20. And all other filters and changes will be applied only for these issues.

I guess I need to create some calculated members with filtering by date, but didn’t manage to create it.

[Anton_Kruglikov]

Resolved, I used jql in import for defining exact date of importing issues

[martins.vanags]

Hi,

JQL filter in import options is a good solution, however, that would affect all other reports on your eazyBI account as well.
Another way to solve this would be by creating a calculated measure that would return the number of issues created in a specific time frame.

You could first create a calculated member in “Time” dimension to aggregate all dates after 20th of Feb

Aggregate(
[Time].[Day].DateMembersBetween('Feb 20 2019','today')
)

And then use this member to create your calculated measure.

(
  [Measures].[Issues created],
  [Time].[After 20th of Feb] --reference to Time dimension calculated member
)

Martins / eazyBI

[Dom_Pun]

Hello, I have a similar challenge and the above solution doesn’t seem to work.

I want to create a filter (part of Pages) that would show only issues created after certain date, say Jan 01, 2022.

I’ve created a calculated member in ‘Time’ as per suggestion above:

Aggregate(
[Time].[Day].DateMembersBetween('Jan 01 2022','today')
)

But when I use it for filtering, it only seem to bring issues that were resolved during that timeframe, not created. It’s probably a simple adjustment I need to make (adding something like [issue created date]). Could you advise?

[martins.vanags]

@Dom_Pun

Report context in eazyBI is usually set by selecting the measure for the report.

If you select measure “Issues resolved” then report results would calculate the number of issues resolved in the filtered time period and the Time calculated member would be using resolution date to filter time periods.

Martins / eazyBI

[Dom_Pun]

Thanks @martins.vanags,

Let me clarify what I’m trying to achieve:

I’m trying to get Average Resolution days and Average days in transition status of issues that were created during specific time period (e.g. from 2022 Jan).

If I use the calculated member in ‘Time’ as described above, it filters for issues resolved, instead of created during that timeframe.

I need to create a different filter, just not sure what formula I should use…

[martins.vanags]

@Dom_Pun

In that case, you would have to create new calculated measures that would know how to behave when “Time” dimension is filtered.

Try this formula for “Average resolution days when issues created” (save the calculated measure with decimal format)

Avg(
  Filter(
    Descendants([Issue].CurrentHierarchyMember,[Issue].[Issue]),
    Not IsEmpty([Measures].[Issue resolution date])
    AND
    DateInPeriod(
      [Measures].[Issue created date],
      [Time].CurrentHierarchyMember
    )
  ),
  (
    [Measures].[Total resolution days],
    [Time].CurrentHierarchy.DefaultMember
  )
)

And this one for average days in transition status if created:

Avg(
  Filter(
    Descendants([Issue].CurrentHierarchyMember,[Issue].[Issue]),
    DateInPeriod(
      [Measures].[Issue created date],
      [Time].CurrentHierarchyMember
    )
  ),
  CASE WHEN
  [Measures].[Transitions from status]>0
  THEN
  Sum((
    [Measures].[Days in transition status],
    [Time].CurrentHierarchy.DefaultMember
  ))
  END
)

Martins / eazyBI

[Stijn]

Hi,

I’m having a same problem here - the solution presented by @martins.vanags seems to work, but that means a calculated measure is needed for every measure I would like to use, where I would need to replicate the predefined measure but with an additional filter on created date? Is this a correct understanding?
This would make it also harder to compare sets of issues (e.g. we have received requests to compare our efficiency in 2022 vs. 2023 - when there is a need for a calculated measure in the Measure dimension to do this, we lose a lot of flexibility in our reporting.

I was hoping to have some kind of calculated measure in the dimension “Issue”, so reports can be made as in the standard / regular way and only use this custom Issue definition.

Many thanks for your guidance already!

[cmoehring]

Same question and thought: can we add a calculated member to the Issue dimension for the desired date range? What would be the code for that?

[martins.vanags]

@Stijn and @cmoehring

Perhaps you could think about introducing a new calculated field that extracts the year of creation date in a new field.

The Javascript for the field could be something like this:

var creatd = issue.fields.created;
if(creatd)
{
var year_c = new Date(Date.parse(creatd)).getFullYear();
}
return year_c;

Then import calculated field as a new dimension to let you filter the report by year of creation.

Martins / eazyBI