Improve Group By Connections Field

[Brandon Moberg]

Being able to use Connections is such a huge improvement, but one challenge is Grouping By a Connections field in a view.

Example scenario

1. You have 3 Jira Product Discovery Projects: Team A, Team B, Team C
2. Each of those products uses a three-tier connection ladder:
   1. Company OKR
   2. Idea
   3. Experiment
3. While the ideas and experiments will vary by project, the Company OKR connection values are consistent across all 3 projects (example: OKR1: Money, OKR2: Views, OKR3: Retention)
4. In Jira Roadmaps, you create a single roadmap for stakeholders to visualize the roadmap for all 3 teams (Jira PD projects)
5. You want to Group By the Company OKR connections field to show stakeholders all of the Ideas under each company OKR
6. The Group By duplicates the Company OKR value by each project even though the values are the same and the Company OKR connection field is global
   1. In this example, the Jira Roadmap ends up with:
      1. 3 groupings for OKR1: Money
      2. 3 groupings for OKR2: Views
      3. 3 groupings for OKR3: Retention
7. This makes the Group By connections field less than ideal

The workaround we're deploying for now can work around this, but it's not ideal:

1. Create a global field (non-connection) called Company OKR
2. Use automation that triggers on a Discovery - Connected link type and copies the {{destinationIssue.issuelinks.first.inwardIssue.fields.summary}} into the global Company OKR field (non-connection)
3. Update Jira Roadmap to Group By the global Company OKR field (non-connection) instead of the connections field

Any plans to address this? TYIA!