how to install external share for Jira in JPD

[Trena Norcia]

how to install external share for Jira in JPD

[Jens Schumacher - Released_so · Accepted solution]

Hi @Trena Norcia 

Take a look at Released. It's designed to share roadmaps and release notes with customers and stakeholders. 

Your customers can log in via Atlassian ID, Google or via email validation and you can restrict portals to specific email domains, ensuring only your customer has access to it. 

Can you can a demo here: https://hub.released.so

[Aaron Pavez [ServiceRocket] · Accepted solution]

Hi @Trena Norcia 

By external share, you mean like OneDrive? sharepoint? file server?

That doesn't exist out of the box. You can paste the link on JPD ideas or find an app in the marketplace for that. 

If you have more details on what you want to achieve, we can give a more complete reply.

Regards

[Trena Norcia]

We do not want to allow anyone on the internet to access a link

We would like the ability to do what we typically do when providing an external link to the client's sprint board or user story, which we do regularly. That link is accessible without any signup requirements via External Share for Jira

[Aaron Pavez [ServiceRocket]]

> We do not want to allow anyone on the internet to access a link

You need to work with your Jira admin and external share admin to no open those links to the public. 

Jira is only accessible to the people you give access to. The files share should follow the same permissions.

> We would like the ability to do what we typically do when providing an external link to the client's sprint board or user story, which we do regularly. That link is accessible without any signup requirements via External Share for Jira

can you expand on this please? You share the JPD board externally? meaning your JPD is open to the public?

Are they part of the contributor role?

Regards - Aaron

[Trena Norcia]

Aaron, thank you for replying.

We do not share JPD publicly. Instead, we send a Jira Product Discovery link, and the client creates a Jira account. However, the email they use is not validated in any meaningful way. So in practice, it’s almost as open as sharing a direct link to a specific board, which is what I'm requesting.

The issue is that the account creation process appears glitchy and doesn’t always provide the best client experience. Since we successfully use external share in Jira to include ticket links in release notes, this is already a seamless access method for our clients. We'd like to use this same process for JPD links.

This issue is becoming more significant each day. We are on a premium Jira account, and we’re hoping to resolve this soon.

Since NLP is not comfortable granting anyone on the internet access to a client's IP roadmap, can you offer options for us?

[Aaron Pavez [ServiceRocket]]

Then, you need to set permissions on anything shared and give them to only the people who need access to the files.

You have invitation links public-> anyone can join JPD with a link.

You invite people to JPD, anyone with the link. Since this cannot be changed, you must look for permissions elsewhere.

I'll assume the people are contributors. read-only access.

As I see it, this isn't a Jira issue. This is how you choose to use the tool and share a link from external sources. 

> The issue is that the account creation process appears glitchy and doesn’t always provide the best client experience.

This is something you need to bring to Atlassian's attention. Please reach out to them for any issues with account creation.