nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Cumulative flagged time per flagged toggle

Kris Olds

Hi there,

I'm looking to produce a report in EazyBI that will show issues that have been in, are currently in, a flagged status.

The idea is that it will start counting the time when it enters the flagged status, until it comes out of the flagged status.

For example, Issue 1 goes into flagged status at 10:00am on 01/01/2023 then gets unflagged at 10:00am on 03/01/2023 that total is 48 hours. That same issue then goes back into flagged status on 15/01/2023 at 11:00am, then comes back off flagged on 16/01/2023 at 11:00am, this time 24hours in flagged.

Theses 2 times would not be added together, but be displayed seperately. I've attached a screenshot below showing a basic layout I would like to achieve.

Screenshot 2023-10-27 085450.png

Does ayone know if this is possible?

Thanks!

Accepted answers

Elita Kalāne - eazyBI Support

Hi @Kris Olds

Thanks for posting your question!
This is what I would suggest you do if you want to build this with eazyBI.

You could start by following steps written in this eazyBI community page - https://community.eazybi.com/t/how-long-issue-was-flagged-to-paused-cumulative/6677/3?u=elita.kalane.

My colleague has written a JS code to fetch the time the issue was flagged and will return the flagged days when Time is used in Rows or Columns. You will need to add this code to eazyBI advanced settings and then import the field "Days Flagged Cumulative" as a measure.

In cases when the issue is currently flagged, and you'd like to return the days since the issue was flagged till today, you could use the following formula when defining a new calculated measure:

CASE WHEN
 [Measures].[Issue Flagged] = "Impediment" AND
 (
   [Measures].[Transition to last timestamp],
   [Transition Field].[Flagged],
   [Flagged].[Impediment]
 ) =
 (
   [Measures].[Transition to last timestamp],
   [Transition Field].[Flagged],
   [Flagged].[Impediment],
   [Time].CurrentHierarchy.DefaultMember
 )
THEN
 DateDiffDays(
   TimestampToDate(
     (
      [Measures].[Transition to last timestamp],
      [Transition Field].[Flagged],
      [Flagged].[Impediment],
      [Time].CurrentHierarchy.DefaultMember
     )
   ),
  Now()
 )
END

This is how your report might look:

Hopefully, this works for you, but feel free to let me know if you have any follow-up questions!

Elita from support@eazybi.com

All comments

Walter Buggenhout

Hi @Kris Olds and welcome to the Community!

How this can be achieved depends very much on what you mean by a flagged status. If you can explicitly identify these as specific statuses, you can definitely build a report based on the out of the box available transition status.

This sample report in the EazyBI demo account for Jira Software illustrates how that may work:

2023-10-27 10_23_25-.png

If you refer to the flagging mechanism that Jira offers to mark an issue as flagged, that is a totally different thing. That is not linked to a status, but sets a value to a custom field.

Hope this helps!

Emre Toptancı [OBSS]

Hello @Kris Olds ,

I don't know if you can do this with EasyBI but I have the perfect solution that works within Jira. Our team at OBSS built Timepiece - Time in Status for Jira exactly for this. You can even use our app's REST API to get the calculated data programmatically and push it into EasyBI.

First, a small introduction:

Time in Status mainly allows you to see how much time each issue spent on each status or each assignee.

tisCloud_StatusDuration_LeadTime_with Estimates.png

You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time, etc.

Among many other report types, Time in Status has the Any Field Duration report that can do duration measurement for any issue field. If you want to measure the duration of each issue's flag, this report is the exact solution for that.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

tisCloud_StatusDuration_LeadTime_Average_TimeGrouped.png

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well. It supports both Company-Managed and Team-Managed projects for Jira Cloud.

Time in Status reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts. You can also get file exports and REST API access. The REST API is particularly useful if you want to build an integration with EasyBI.

Timepiece - Time in Status for Jira

EmreT

Kris Olds

Hey Walter, thanks for the reply!

Sorry! For more clarification I mean time flagged impediment that sets a custom field, not a status.

Walter Buggenhout

That is a bit what I was getting from your description. So, no worries @Kris Olds. I don't have a working EazyBI instance at hand right now, but I set up a sample scenario that I know should work.

Setting or removing a flag on an issue is essentially an update of that same issue. If you create 3 custom fields (something like "Impediment start", "Impediment end" and "Impeded time"), with a relatively simple automation rule you can capture the start and end times of each flagged cycle, storing it on the issue itself.

Here's an example of what that rule may look like:

2023-10-27 13_24_21-Automation - Jira.png

For both date fields, set the value to {{now}} when you update them. The calculation of the Impeded time may be something like this:

{{#=}}{{issue.Impeded Time}} + {{issue.Impediment Start.diff(issue.Impediment End).hours}}{{/}}

Once you have these calculated values in your issues, it is pretty straightforward to use them for reporting in EazyBI as well.

Elita Kalāne - eazyBI Support

Hi @Kris Olds

CASE WHEN
 [Measures].[Issue Flagged] = "Impediment" AND
 (
   [Measures].[Transition to last timestamp],
   [Transition Field].[Flagged],
   [Flagged].[Impediment]
 ) =
 (
   [Measures].[Transition to last timestamp],
   [Transition Field].[Flagged],
   [Flagged].[Impediment],
   [Time].CurrentHierarchy.DefaultMember
 )
THEN
 DateDiffDays(
   TimestampToDate(
     (
      [Measures].[Transition to last timestamp],
      [Transition Field].[Flagged],
      [Flagged].[Impediment],
      [Time].CurrentHierarchy.DefaultMember
     )
   ),
  Now()
 )
END

This is how your report might look:

Hopefully, this works for you, but feel free to let me know if you have any follow-up questions!

Elita from support@eazybi.com

Mehmet A _Bloompeak_

Hi @Kris Olds

Welcome to the Atlassian Community!

As an alternative, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Time in Status for Each Issue report. For further details, please check Status Time Reports How to Videos.

This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
You can set different duration formats.
You can export reports in CSV file format and open them in MS Excel.
You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Free.

Hope it helps.

Kris Olds

Hi @Walter Buggenhout thanks for the reply. Sorry if I'm being a bit dumb here, if we were to setup custom fields, and add time to the 'Impeded Time', wouldn't that be a cumulative total of all the times it was flagged duration, rather than seeing each individual flagged duration for that issue? I hope that makes sense.

Kris Olds

Hi @Elita Kalāne - eazyBI Support

This looks to be exactly what I was after, thank you very much!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud