Custom Field via Automation for Count of Unique Assignees on Child Issues in an Epic

[mborinstein]

I would like to know how many unique engineers have worked on all issues within an epic. Is there a way to use Jira automation to build a custom field on an epic that captures the # of unique assignees that have worked on any child issue of that epic?

[Bill Sheboy]

Hi @mborinstein 

If you wanted to measure this value from this point forward, you could:

• add a multiple-select user custom field to the Epic
• create rule #1 where when a child work item is assigned, update the parent Epic to add a selection for that assigned user; this could be further restricted by engineer users with groups, lookup tables, etc.
• later when the count is needed, use rule #2 which counts the selections in the custom field

To measure this for existing Epics, the approach described by @Marc - Devoteam to check the changelog history could be used...or investigate marketplace apps which can perform this type of analysis.

Hi @Marc - Devoteam -- In my experience, when teams have individuals (rather than pairs / mobs / teams) work on work items, counting this measure may help manage several of the Lean wastes: delay, task switching, motion, over processing, and management activity. (And perhaps also the others too: inventory, defects, and over production.)

Kind regards,
Bill

[Marc - Devoteam]

Hi, @mborinstein 

Theoretically probably.

You would first need to get all issues and then branch over all the issues and within the branch create a web request to get each of the issues change logs and find all assignee changes.

Then would would need to store those in a variable, then remove all duplicates.

It will be messy and probably will fail at times.

My real question is why, what would this KPI bring you?