Count transitions on field Team

Hi @Alsu_Zaynutdinova,

​If you want to track the transitions of an issue between teams, you need to import the change history for the field Team.
​Please read more about setting up change history import here - Advanced settings for custom fields.

​This will allow seeing how many teams have worked on or at least been assigned to the issue.

​The measure “issues created” will link the issue to the latest assigned Team.
​The measure “issues resolved” generally counts issues towards the team where the issue resolution took place.

The third line of your expression is missing the level for the members of the Teams dimension.
​Probably, you might use the following line instead.

​[Team].[Team].Members, ​

​However, this calculation would only show the number of teams assigned to the specific issue (set).

​If you are looking for the number of issues resolved by a specific team split by the number of teams worked on the issue, you need to iterate through the Issue dimension to identify issue relevance to the report context and then check the number of assigned teams.

​The expression for finding the number of issues resolved with “X team efforts” might be as follows.

Count(
​ Filter(
 ​ DescendantsSet(
​   [Issue].CurrentHierarchyMember, [Issue].[Issue]),
​--condition to determine issue relevance to report context - team on rows and possible filter on Time
​ [Measures].[Issues resolved] >0
​ AND
​  COUNT(
   Filter(
     [Team].[Team].Members,
      ([Measures].[Transitions to],
        [Transition Field].[Team],
        [Time].CurrentHierarchy.DefaultMember)> 0)) = 
--number of teams worked on issue
    1
​)

​Since the measure “Issues created” relates to the current Team of the issue, tracking the number of issues created by the specific team and then being assigned to multiple teams is trickier as that also requires finding the first Team. I suggest creating an additional JavaScript-calculated custom field to find the “Creator team” already during the data import in that case.
​Please see a community thread about importing the first “owner” here - first user assigned to issue - #2 by martins.vanags.

However, these measures might still not be very clear for splitting efforts by teams as they give the same weight to the teams completing 99% of work or not doing anything at all while possessing the issue.
You might look for the time logged against the issue to see the involved teams better.

​Regards,
​Oskars / support@eazyBI.com

2 Likes