Difference between Linked issue and Linked items and Workflow Condition for Linked Issues

[#1]

Hi Community! I would also like to draw your attention to the fact that Linked Items and Linked Issues are distinct. The linked item is part of the JPD system field (formula type) and is not applicable to JSW projects.

JPD System Field Details(Linked items)

This field is specifically designed to track the number of work items associated with JPD ideas. I am attaching a screenshot for your reference from a test JPD project showing the count and description of the custom field, which results in an error on the screen for JSW projects:
 

                 Message on JSW screen when adding JPD field (Linked items)

                   Custom Field explaining the field type and supported Product

                                                  How it looks in JPD projects

The most common use case where a Customer wants to use this field is to see if the field is populated before allowing users to move ahead with the transition.We have an open feature request to support Linked issue(s) for the field to better support in validators/conditions, as the field does not appear in validators.

• JRACLOUD-71554 Workflow condition/validator for Linked Article/Issue

So, if you are trying to block a transition when the work item does not have linked items, and based on this assumption, I tested an option to add a restrict transition rule. This rule allows you to check if the numbers are greater than a value before allowing transition, as shown below:

The only caveat is that this workaround will remove the transition on the configured status without providing any warning to users.

As a workaround, you can use a read-only text field on the screen to give some notification.

I have attached a video snippet of the setup, where the "Todo" transition will only be available to a user if there are linked issues.

[Bill Sheboy]

Hi @Waqas Mahboob -- Welcome to the Atlassian Community!

The Linked Work Items / Work Item Links (formerly called Issue Links, and still named "Linked Issues", issuelinks, etc. in different contexts) has been around for a very long time.

After the unfortunate decision to rename "issue" to "work item", why would Atlassian add the field name you note for a specific product, Jira Product Discovery (JPD), potentially leading to usage confusion?  The term "item" is now in both...apparently necessitating the need to write articles explaining the fields.

Thanks in advance for your prompt and relevant reply.

Kind regards,
Bill