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; } } }

Link to an Idea from a Jira ticket

Gary Spross

Is a JPD license required to be able to link a Jira ticket to an Idea from the Jira ticket (not from the Idea)? I assumed a JPD license wouldn't be necessary for this action, otherwise, why allow linking to Ideas from the delivery tickets? A Jira licensed user within a Jira project sees this option and can view an Idea, so they want to match their work ticket to the Idea, but can't do it themselves? Instead they need to either get licensed to JPD or ask someone with a JPD license to link it for them?

I know that editing an Idea is permissible only to licensed users. I'm guessing linking to an Idea is considered editing the Idea, therefore this action requires you to be licensed?

If this is actually the case, I would hope Atlassian would see this as an issue and make an update to allow contributors to contribute to the Idea by linking their work without requiring them to be JPD licensed.

Accepted answers

Nick Haller

Hi @Gary Spross ,

I believe this would be more of a Jira permission based on the workflow you mentioned; linking an idea from the Jira ticket.

If you were to add this user(s) or group(s) to the project's Settings >> Permissions tab >> Link Issues permission, and retest - do you run into the same issue?

Tanguy Crusson

Hi @Gary Spross unfortunately we don't have much control over this behaviour: the Jira Platform doesn't let you search and link issues if you're not licensed for the product that is hosting these issues.

Jet_m3qoex

@Gary Spross This is currently not possible, however I agree that contributors should be able to link ideas from the Jira ticket. We are going to investigate and try to fix it in the next sprint. I will let you know when it's done.

All comments

Nick Haller

Hi @Gary Spross ,

I believe this would be more of a Jira permission based on the workflow you mentioned; linking an idea from the Jira ticket.

If you were to add this user(s) or group(s) to the project's Settings >> Permissions tab >> Link Issues permission, and retest - do you run into the same issue?

Tara_Westgate

@Nick Haller having the same issue when Delivery Team Project (JS) Member trying to link an issue to and Idea, I even tried using the link issue ( "added to idea", implements" etc) - No JPD results are found

Deets:

JS Delivery Project = Company Managed Project

- Validated global linking permissions turned on

-Validated Project perms (role and groups based) - on for linking & browse role and group level

*project team members are Contributors on the associated JPD

JPD = Access = Private

Nick Haller

@Tara_Westgate I'd assume this is a permission issue then because linking to ideas is a creator permission - and due to the user having Jira permission, but not JPD permission - could be the cause.

It'd be worth testing the same scenario / workflow to see if a creator can add the link, and not the contributor.

Gary Spross

The users in question are in a role that has the "Linked Issues" permission within the development projects. When they attempt to link to an Idea from a JPD project, the Ideas don't show up in the list. Even if they type the Idea key, they are not able to add the link.

Gary Spross

In my case, yes, a creator can link the issue. The Contributors cannot. So in order to allow someone to just be able to link, then they need to be licensed to JPD and made a Creator within the project. Linking should not require a JPD license (in my humble opinion).

Screenshot 2025-01-11 143805.png

Tanguy Crusson

Gary Spross

Oh, I would've thought that as a Contributor you could do searches and find JPD issues associated with projects you are able to access (since you can view them within the project). Based on that, I was thinking you should be able to find those same JPD issues and link them from the development (Jira Software project) issues.

Jet_m3qoex

Gary Spross

Thanks @Jet! Appreciate the response.

Rens Hendriks

Currently for us it is also blocking for our current process, agreeing fully with @Gary Spross hopefully this will change in the future! would be very handy and in my opinion critical especially for Product + Design + Engineering collaboration all sitting in the Delivery phase.

Tere Pile

Posted similar in another post - this used to work (or maybe I'm dreaming) but I think there are 2 use cases

I am a JPD Creator

* I can link work item via delivery in JPD (still works)

* I can link work item via epic to JPD (no longer works) - tried all of the Polaris 'links' idea for or implemented by nothing, I mean it links, but it doesn't show up in delivery (and it used to) This was a big plus for our tech team who worked in both worlds

I am a Tech lead w/Contributor

Never tested this because the above worked (my bad) but I want my leads to see the ideas and play a role, but they in no way need a JPD license. I just want them to ensure once delivery epic created, they can "link" it to the idea (i.e. w/in the software project)

This is a set back.

richie.gee

Hi @Jet

Would you be able to share the timeline or the ticket where we can follow the progress of the implementation?

This is currently a blocker for us to push JPD for wider adoption within our organization.

Thanks.

Chithalka Nilindi

Hi @Jet ,

We are facing the same issue as @Gary Spross and @richie.gee. Unfortunately, we are unable to fully roll out JPD in our organization because our contributors cannot link delivery Jira tickets to ideas.

Could you please prioritize fixing this issue on your end? We would really appreciate it.

Thank you.

Chithalka Nilindi

Hi everyone,

We discovered a way for the contributors to link delivery tickets in Jira to ideas within the delivery ticket. Here is a step-by-step guide on how to do it:

Step 1 - Navigate to the delivery ticket in Jira and click the "+" icon. From the list of available options, select "Link issue".
Step 2 - First, choose "implements" as the link type. Next, enter the URL of the idea in the "Search for issues" bar. Finally, click the "Link" button.
Step 3 - Once the link is created, the idea will appear as a linked issue within the delivery ticket.
Step 4 - You can click on the idea to navigate to it and confirm that the delivery ticket is listed under the "Delivery" section within the idea.

Hope this helps!

Andrej_fyaruk

Works! Thank you

Jet_m3qoex

@Gary Spross @Rens Hendriks @Tara_Westgate @richie.gee @Tere Pile @Andrej @Tere Pile

We have found a solution to the problem and it's been released to all Jira users.

Jira users are now able to link JPD ideas as contributors.

Known limitations

It will not work for ideas in Private projects even if the user has been added as a contributor on those projects
- Good news, we will address this problem in the next sprint. Changing permissions is a risky business that needs a lot of care. Hence why we decided to not change this all at once in the first version.
It will not work for Limited projects that were created before this feature got to production, but there is a workaround: If the project access level is changed to another access level and then moved back again to limited, then it will also work.

Gary Spross

Awesome news!

Thanks for this follow up!

Tere Pile

Progress - it is a private project currently but will have to wait for Private.

I have a limited creator role configured to mitigate changes in our project. Given configurations we have all creators are 'limited' unless I give them specific access to project as full creators. So to use the Limited project access means all creators become contributors, which messes up my logic. I could work around it but waiting is less painful right now.

Michael Mackuliak

@Jet - any update on the fix for Private projects? Unfortunately we have to have private projects as we have some 3rd party consultants in our Atlassian deployment and dont want to have _any_ visibility to our JPD projects.