# Count of issues updated more than 5 days ago

Thanks in advance for any help that can be offered here. What I am trying to do is get a count of how many issues have not been updated in five days by priority.
We have several issues with multiple priorities like major, minor, etc. How would I go about getting a count of something like this?

``````                   Count
``````

Critical 2
Major 5
Minor 10

Sorry about the formatting of my table. I was trying to show an example of my desired output. Essentially, I would like to get a something that says there was 2 critical issues with a last updated date of 5 days ago, 5 major issues with a last updated date of 5 days ago, and 10 minor issues with a last updated date of 5 days ago.

You could achieve this with a calculated measure that uses the PreviousPeriods function. It would create a set of the Time dimension Day level members that are five days and more from now. Then the Sum function would calculate the measures â€śIssues last updatedâ€ť values for each set member and return the sum. Finally, you could subtract the â€śIssues resolvedâ€ť measure to get the count of all open issues. Please have a look at the code below:

``````Sum(
PreviousPeriods([Time].[Day].CurrentDateMember.Lag(4)),
[Measures].[Issues last updated]
)
-
[Measures].[Issues resolved]
``````

Kind regards,
Roberts // eazyBI support

This measure is great - thanks.

How could I make the measure a time period (i.e. now to 30 days, 31 days to 60 days, etc).

So one measure for 31 days to 60 days, and another measure for 61 days to 90 days?

Thanks

Mark

Hi @MarkWheeler,

You can either define several calculated measures with a similar construct or define a new JavaScript calculated interval dimension.

For a calculated measure, the formula could look similar to the one below:

``````Sum(
{[Time].[Day].CurrentDateMember:[Time].[Day].CurrentDateMember.Lag(6)},
[Measures].[Issues last updated]
)
``````

It will return the number of issues updated in a seven day period (today - six days ago). See the eazyBI documentation page on calculations with Time dimension - https://docs.eazybi.com/eazybi/analyze-and-visualize/calculated-measures-and-members/calculated-members-in-time-dimension.

Several such calculated measures could negatively affect the report load time. In such a case, you may want to pursue the JavaScript calculated interval dimension option. The calculation then would be done during data import instead of report execution time. See more details on interval dimensions here - https://docs.eazybi.com/eazybijira/analyze-and-visualize/interval-dimensions.

And here is our documentation page on defining a JavaScript calculated interval dimension in the eazyBI advanced settings for issue updated age - https://docs.eazybi.com/eazybijira/data-import/custom-fields/javascript-calculated-custom-fields#JavaScriptcalculatedcustomfields-Customcalculatedfieldasanintervaldimension.

Best,
Roberts // support@eazybi.com

Hi @roberts.cacus ,
I have a similar question to the original one in this thread: I am looking to create a time filter, which will present only the JIRA tickets which havenâ€™t been updated in 6 months or more.
As you can see in the screenshot below, I set up a report which shows me all the tickets which were created over months ago. Can you think of a filter which will help?
Thank you,

-Noam

Hi @Gnome ,

In your case, I suggest subtracting the number of issues updated in the last six months from the total number of issues last updated. The formula for a new calculated measure could look similar to the one below:

``````NonZero(([Time].CurrentHierarchy.DefaultMember,
[Measures].[Issues last updated])
-
Sum(
{[Time].[Month].CurrentDateMember:[Time].[Month].CurrentDateMember.Lag(6)},
[Measures].[Issues last updated]
))
``````

You can remove the Time dimension from the report pages, as the calculated measure will reset the context for it anyway.

See the screenshot of the report below:

In my environment, I have only issues in the â€śDoneâ€ť status updated more than six months ago in my environment.

Best,
Roberts // support@eazybi.com

1 Like

Thanks @roberts.cacus, it works perfectly.

-Noam

1 Like