nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Linked Issues" vs "Linked issues"

Kelly Arrey

Hi @Tanguy Crusson and community,

"Linked Issues" (upper case I) is a Jira field which has been around for many years. It displays the keys of issues linked to the current issue in a Jira filter report.

"Linked issues" (lower case i) is, as far as I can tell, a relatively new field introduced by Jira Product Discovery. This field displays the number of issues linked to an idea.

Having two fields with almost identical names (with wildly different semantics) is something that most Jira admins recognize as a bad idea, and they wouldn't allow it on their Jira system. Thus it's very surprising to find that this "worst practice" was implemented by Atlassian. I would argue that this is a bug, but in any case, Atlassian has taken it as a "Suggestion", JPD-124. If you'd like to see this fixed, please watch it and vote for it. And Tanguy, would it be possible to open comments on the JPD project?

Thanks,

Kel

Accepted answers

All comments

Nick Haller

Hi @Kelly Arrey ,

Sorry for any inconvenience this has caused. I've added your feedback above to the feature request JPD-124, and hopefully engineering considers this in the near future.

The Community is the best place to monitor for JPD product updates and releases such as these most recent few:

JPD feature requests and bugs are not publicly available / only internally facing as this time.

Kelly Arrey

Thanks @Nick Haller !

TBH, I'm not sure I understand what "Gathering Interest" status means if the tickets are internal only.

Kelly Arrey

@Nick Haller @Tanguy Crusson

With all due respect, I have to ask what's going on? I now see 4 fields with an overloaded name - the problem is getting worse, not better.

HELP!!!

Kelly Arrey

Hi @Tanguy Crusson,

Any comment on the above? This should be a straightforward fix, right?

Thanks,

Kel

Jon Irusta

I do absolutely agree with you @Kelly Arrey . Thank you for reporting this issue!! My team would like to have visibility of the https://jira.atlassian.com/browse/JPD-124 issue please.

Thanks in advance!

Drew Kerrigan_4tg868

@Kelly ArreyThe problem you're referring to here, is because Jira Product Discovery is now partially behaving like the poorly designed "Team Managed" projects and creating ephemeral non-managed fields that it then dumps into the JQL system allowing for free flowing un-managed namespace collision fields.

I say "partially" because it decided to take that worst practice a step further and automatically create ephemeral namespace colliding fields that cannot even be renamed or deleted.

So you're getting a new "Linked issues" field for every Jira Product Discovery project that gets created in your site.

@Nick HallerI can't see what y'all have in the JPD-124 ticket but please consider making the ultra minor fix to just rename this "Linked issues count" or anything else instead of what it is. It's creating a terrible UX in Jira Searches.