Running into some issues with JPD connected fields (using it as a Global Field).

[Elyse Algate]

Problem 1 - limit of 20 spaces for Global Field setting: 
We're trying to use Global Connected fields for several Jira Spaces within JPD (over 20). We get an error that says "You can't select more than 20 spaces" when we try to add more than 20 Jira Spaces as the Source in our Global Field setting. 

We can apply the global field to 200 spaces. The connections don't work if they are not tied as a source in this section though. 


Problem 2 - What determines which Fields you can add in the "Connections" tab in the screenshot below? We don't have the ability to access / add all of our fields in this section and cannot determine the logic that enables fields to show up here. 

Problem 3 - We want to better understand the parent/child relationship between the parent hierarchy and child hierarchy for connected fields. We tried to mimic the example below from the JPD demo, but everything shows up in "No Values." 
- We are currently only tagging the 2nd layer (in this example - iterations) as Q1, Q2, Q3, or Q4. When we do this (and turn on the "match column" filter, the initiatives all show up in "No Values". Other things we've tried causes nothing to show up in this view. 
- We can get around this by manually tagging the 1st layer (Initiative) with the corresponding Q1, Q2, Q3, or Q4 from it's child Iterations, but that is very manual. It seems likely there is a better approach; we may just be missing something in how to set up the connections correctly. 


We appreciate any help from the community! Thank you so much. 

[Tanguy Crusson · Accepted solution]

Hi @Elyse Algate ,

Problem 1 - limit of 20 spaces for Global Field setting: 

We're going to work on that - unfortunately it's not an easy fix today, but we have this on our roadmap to start straight after we get out of beta

Problem 2 - What determines which Fields you can add in the "Connections" tab 

If you are connecting ideas between different projects you can only see their global fields, not project fields. Could that be what's happening for you there? 

Problem 3 - We want to better understand the parent/child relationship between the parent hierarchy and child hierarchy for connected fields.

Today connections are not transitive: basically on the screenshot you shared you'd need to tag the initiative with Q1, Q2, Q3 (multi-select), and tag each iteration with their respective quarters.

It's something we have in our sights for after we take this feature out of beta

[Elyse Algate]

Hi @Tanguy Crusson - Thank you for the quick response! That does answer all our questions. We're really loving the connection feature and look forward to future releases once it is out of beta!