Help with Tracking Status Changes

[bcobrien1977]

Hi,

I am trying to track staus changes over time for a list of projects and indicate for a month how many projects started and here is how they landed at a month end.  Here is a snapshot of the data where I want to look at the date fields to show where something was at a particular date and the string fields to show the status. 

IssueKey	Summary	OldString	NewString	StartDate	EndDate
EITEAM-10	Stability	Ready for PI	PI Committed	7/29/2022	8/31/2022
EITEAM-10	Stability	PI Committed	In Progress	8/31/2022	11/30/2022
EITEAM-11	Change	Ready for PI	PI Committed	8/15/2022	8/31/2022
EITEAM-11	Change	PI Committed	Done	8/31/2022	12/10/2022

For the output I basically need to bucket each project and then I would probably assign numerical values to each status to take the difference between the starting stage (Ready for PI) and the last reported stage .  I can't seem to get the measure to work correctly.

Can anyone provide some guidance?  Thanks

	Desired Output
	31-Jul	31-Aug	30-Sep	31-Oct	30-Nov	31-Dec
Ready for PI	EITEAM-10
PI Committed		EITEAM-10	EITEAM-10	EITEAM-10
In Progress					EITEAM-10	EITEAM-10
Done
	31-Jul	31-Aug	30-Sep	31-Oct	30-Nov	31-Dec
Ready for PI		EITEAM-11
PI Committed		EITEAM-11	EITEAM-11	EITEAM-11	EITEAM-11
In Progress						EITEAM-11
Done

[v-jingzhang]

Hi @bcobrien1977 

Is it possible that some status can be skipped? In your example of EITEAM-11, the status after "PI Committed" is "Done", it doesn't have "In Progress" row. Is this a correct result? Is this possible to happen on other issues? 

In addition, for "EITEAM-10", does it have a row with an old string "In Progress"? In your example, it seems "In Progress" is the last and current status for "EITEAM-10". I wonder if every issue has a row for its last status? 

I intend to make every issue have a row for every status it experiences and each status row have a start date and end date. 

Best Regards,
Community Support Team _ Jing

[bcobrien1977]

Hi,

That is part of the problem that you can move through more than one status.  So basically you could move from two spots simultaneously. I know this is not totally logical but basically it has to do with delays in stafff entering the data. 

Yes, you are right on the E-Team 10.  

Another way to think about it is.....

If you had 100 projects at the start of the quarter, how many ended up at each stage?

Thanks