You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
I have several Jira Product Discovery (JPD) projects set up, and when you create a field in that product, behind the scenes a custom field is created in Jira that can be queried via Filters/Issue Search.
Across my projects, I've used the same name for several fields, so that PMs moving between projects have consistency. For example, there's a "Product Strategy" field that exists across 3 different JPD projects. This in turn creates 3 separate custom fields, that look something like this:
The tricky part is that when you go to select a column in Filters/Issue search, it appears that Jira collapses these 3 separate custom fields into one selectable entry:
I assume this is done to hide from users the fact that the "*Product Strategy" column is really 3 separate custom fields.
This causes 2 issues:
As a result, I'm wondering if there's any way to select the specific custom field as a column in the table in Filter/Issue Search?
There is no way to choose a specific field by customfield ID as a column.
In general, I would strongly advice against using duplicate field names. The issues you listed are only issues because several fields have the same name.
If a field should hold values that can be labeled as "Project Strategy", then this one field should hold said values for all projects imo. Setup different contexts if the specific values need to differ from project to project.
Then again, add a grain of salt, because i fail to understand what the following means (to clarify, one field called "Project Strategy" provided in all necessary projects would achieve the same, if i understood it remotely correctly - so i assume i did not):
PMs moving between projects have consistency
Thank you Michael for the context, that makes sense. The tricky part here is that custom fields with Jira Product Discovery work a bit different at the moment that traditional custom fields.
For now I'll just have to live with that fact.