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

Developers linking to JPD Idea

Michael Mackuliak

Our developers are seeking to link a delivery ticket (in Jira) to a JPD idea. The goal is to then have that delivery ticket show up in the 'delivery' tab of the JPD idea.

It seems that this functionality is only available if they are given a creator licence. Which feels like a waste of a seat, they wont be going into JPD to create, view or edit ideas in general.

Is there a way to make this work without giving them creator access?

Accepted answers

All comments

Sahir Maharaj_28wu8p

Hello @Michael Mackuliak

Based on my understanding, linking Jira tickets to JPD ideas often requires creator access for full functionality.

However, you can explore using automation rules or API integrations to establish this connection without granting additional access.

Gary Spross

@Michael Mackuliak, coincidentally I just recently asked the same question. One of the responses from Atlassian indicates they are aware that this is not possible and are investigating a potential solution. Fingers crossed!

Nick Haller

Hi @Michael Mackuliak ,

You are correct. Creating deliveries does require a JPD license.

I think a way to essentially bypass granting additional JPD licenses is through automations - as long as the Actor of the automation has JPD permissions (whether that is the A4J user or a creator).

The automation could execute when a JPD idea is linked to the Jira issue, then updates the link-type to "implements" by the Trigger issue - which is the connection between Jira issues and JPD ideas through deliveries.

Might look something like this:

1) WHEN: Issue linked (Select link-type(s). Could also add an IF component under this step that validates the project-type is for JPD ideas only)

2) BRANCH rule / related issues:

Type of related issues = Linked issues
Link types = (Select same link-type(s) in step 1)

3) THEN: Link issue to:

implements - Trigger issue

4) AND THEN: Delete issue link(s)

Select same link-type(s) is step 1 and 2

^ This step removes the additional linking.

I understand this is a bit wonky of a workaround, but should avoid having to add additional JPD licenses.

Again, this is just an example of what could be configured. The automation could instead execute when another field is updated, and add the Jira issue link to the JPD idea as implements - but the automation needs to identify which idea to add to. This is why my example uses the link-component since the automation can easily identify it.

Hope that helps!

Nick Haller

Hi @Gary Spross ,

I had responded to that previous post, and did not think of a workaround until this Question. Maybe the suggesting I provided in this post will help in the meantime!

Gary Spross

I appreciate the workaround, but I definitely think this is functionality that Atlassian should implement by default.

It would also be helpful if there was a specific permission for linking Ideas to control who is allowed to perform this action. To me, even though it is just an issue link, it's a bit more than that since it's involving JPD tickets. I can see situations where only senior level engineers should be able to make that decision.

Michael Mackuliak

Thank you Nick for the detailed suggestion. Will try giving this a whirl but am hoping that in the other thread Gary shared this gets fixed (as tentatively promised) by the Jira team.

Thanks again - really appreciate the detail and fast responses you and the team always provide.

Tere Pile

This worked previously where developer could use 'is idea for' the Polaris link and it would show properly in delivery. Now based on this discussion seems requires a JPD license, that defeats the purpose of separation of duties where planners plan and delivery delivers. It puts extra work on the planners to manage their ideas that was previously functioning.

To me this is bug not a new feature

Matthew Stinchcomb

@Nick Haller

Hey Nick,

Appreciate the response and workaround here, about to go test it myself, I do have a questions will it still allow the to trigger automation if they don't have access to link because of the license restriction to a discovery project?