Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

Elyse Algate November 12, 2025

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. 
1) Source Space Error.png

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. 2) JPD Connections - Connections Tab.png

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. 
3) Parent-Child Tagging.png

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

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events