Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Sharing portal links and access rights

I have both Jira SW and JSD.

Most of the time, if people are not member of the team handling the JSD tickets, when I give them a ticket ID, they come back to me because they can't find or can't access it.

The ones who can't find it usually tried the search in the JSW view and that will not return any result as they are no agents. The others usually tried to edit a "browse" link and were returned a lock page with the message "you don't have access to this issue".

They are registered as customers on the JSD project, not as agents. Wouldn't it be great that when looking for a JSD ticket you get presented a portal link rather than a browse link? By default, as an agent, the portal view allows to switch to the agent view, but the reverse is not true.

Either the Jira search should detect that the ticket is only accessible in the portal for that user and transparently switch to that view, or else the default for tickets should be a portal link... 

It is even worse with the Slack plug in. I intentionally paste the portal link, but the plugin adds a summary that is also a link. But instead of pointing to the portal, the link of the summary points to the agent view!!! so in almost 100% of the cases people tell me they can't access!



My JSW users are developers and use a JSD project with the same login, but as customers of my infrastructure.

Claudio Gonzalez
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Jul 29, 2021

For our organization we have the same situation. But:

1. we use https://<instance-jira>/browse/<ticketJSM> (only to users with JSW license)

2. we add user how "Shared with" from the portal site

Screen Shot 2021-07-29 at 04.19.33.png

to users without license JSW.

Daniel Ebers
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 30, 2021

Hi @Bernard Clabots

testing on my Jira Cloud instance I was recently able to reproduce what you are observing.
However, I felt it got much better to handle as soon as I put the users (those that normally use Jira Software) per Permission Scheme and then via a role in the Jira Service Management project to one that allows for browsing (Browse Permission).

Then they are able to browse a Jira Service Management project - however, without any customer facing features where they would need a Jira Service Management license assigned to them.
As soon as I did it "non-agents", in other words the users of Jira Software >in< the Jira Service Management project, could also start using the search. Also the user interface is the familiar one they know already.

Does this help in your scenario, can you compare with what you have configured perhaps?


Like Bernard Clabots likes this


  I configured it that way for the moment.




Log in or Sign up to comment
AUG Leaders

Atlassian Community Events