Issues created or modified after a certain date

Here is the JQL I am trying to emulate with eazyBI. This returns all issues that were either created or updated since Apr 1st 2024:
project in (List of proejcts ) AND issuetype in (Task, Defect, Story) AND (updatedDate >= 2024-04-01 OR createdDate >= 2024-04-01)
Could someone help me do this in eazyBI?
Note: I can get issues that fullfil each of the above conditions seperately but I need them together. For this I used the Issues Created measures and a user defined Time measure like so
Aggregate([Time].[Day].DateMembersBetween(‘Apr 1 2024’,‘today’)). I can do the same with Issues Updated measure. But how do I get both issues created after Arp 1st 2024 and issues modified on/after Apr 1st, 2024 together without double counting?
For e.g. the 6 Issues Created in row 3 are the same 6 that were updated since Apr 1st 2024. I want to see just 6 not 12. (Note I only have the columns side by side for testing. In reality I just want one column that does not differentiate between created and updated)

Delivery Category Issues Issues
last created
updated
XXX 635 4
XXXX 1
XXXXX 6 6
XXXXX 6 4
XX 110 102
XXXXXXX 2 1
X 410 254
Total 1,170 371

Hi,

A custom formula will be needed to count issues that are either created or updated after some date.

We will need to iterate the issues and apply the condition, so the formula like this should work:

NonZero(Count(
  Filter(Descendants([Issue].CurrentMember,[Issue].[Issue]),
  [Measures].[Issues created]+[Measures].[Issues last updated]>0
  )
))

This formula assumes that you use the aggregated member in the Time dimension:

It is recommended to use FuturePeriods function to aggregate the periods after some date. Your solution with the day-level aggregate is also correct, but this version should be more efficient:

Aggregate(
  FuturePeriods(
    [Time].[Day].DateMember('Mar 31 2024')
  )
)

Kindly,
Janis, eazyBI support

Thanks Janis, this makes sense but since we are not on the cloud as yet I do not have the FuturePeriods function…is there an alternative?