Request - Better Links/ URLs
Asked by Ben Arundel:

Hey

I'm sure we're all very happy with how JIRA does URLs

It's usually <https://you.atlassian.net/browse/ISSUE-KEY>

In JPD it looks like this for a sharable link:

[https://you.atlassian.net/jira/polaris/projects/PROJECTKEY/ideas/view/999999?selectedIssue=ISSUE-KEY\&issueViewSection=comments\&atlOrigin=SOMEUID](https://you.atlassian.net/jira/polaris/projects/PROJECTKEY/ideas/view/999999?selectedIssue=ISSUE-KEY&issueViewSection=comments&atlOrigin=SOMEUID)

And this is from the address bar:

[https://you.atlassian.net/jira/polaris/projects/PROJECTKEY/ideas/view/999999?selectedIssue=ISSUE-KEY\&issueViewSection=comments](https://you.atlassian.net/jira/polaris/projects/PROJECTKEY/ideas/view/999999?selectedIssue=ISSUE-KEY&issueViewSection=comments)

It would be great to have nicely formatted URLs


Answers:
author: Ian Sperry
body: Yes a thousand times yes. The URLs contribute to a more negative experience when a 3rd party tool is trying to ingest them.

In Miro for example I cannot just paste the shareable link from JPD to create a card on the whiteboard, it instead interprets it as I am trying to paste a list. It works better with links from JIRA.

comments: author: Rylan Maschak
body: I have the same issue with Miro... and sometimes in Confluence it doesn't appear to resolve either.


author: Steven Chang
body: Hi [@Ian Sperry](/t5/user/viewprofilepage/user-id/4559137) [@Rylan Maschak](/t5/user/viewprofilepage/user-id/1455349)! Steven from Miro here. Are you using JPD URLs from the same Jira instance that is connected to your Miro accounts?


author: Rylan Maschak
body: [@Steven Chang](/t5/user/viewprofilepage/user-id/5148657) Yes, I am.


author: Ian Sperry
body: [@Steven Chang](/t5/user/viewprofilepage/user-id/5148657) Yes I am. In order to add JPD cards to a board I need to search for the issue key in the Jira app in Miro and cannot just paste the URL.


author: Steven Chang
body: Hi both. I would love to know better what the format of the URL you are using is. Feel free to book a quick chat with me here: <https://calendly.com/miro-steven-chang/chat>  

Thanks!


author: Jan-Hendrik Spieth
body: I understand the issue, and see it the same way. Some parts of the links ("atlOrigin=SOMEUID") clearly seem dispensable/optional, from our users point of view.

But the part with the view ...?

I think one issue here is that there is no single default view for a JPD project - not in the way JSW or JSM projects have that one "list of issues". JPD projects can configure any views they like.

Note how a link to a JSW/JSM issue, like <https://you.atlassian.net/browse/ISSUE-KEY>, brings you to the "Issues" view, as indicated in the project sidebar:

![Screenshot 2023-02-08 223230.png](https://community.atlassian.com/t5/image/serverpage/image-id/239111i88F58E666012EFEB/image-size/large?v=v2&px=999 "Screenshot 2023-02-08 223230.png")

So the question would be: if JPD links don't include a view parameter - which (list) view would you want an idea to open in, for your project(s)?

Side note: we're [not the first to bring this up](https://community.atlassian.com/t5/Jira-Product-Discovery/A-little-list-of-functionality-available-in-Jira-Software-that-I/td-p/2229625) :-) [@Rohan Swami](/t5/user/viewprofilepage/user-id/2842658), can you maybe confirm that you put this to the backlog, indeed? If so, what's the solution going to look like? :-)

comments: author: Ian Sperry
body: I think JPD just needs a permanent Issues list to open in. I just had a situation in which this happened

* The last list I was looking at was the Archive.
* Then I click on a link to open an idea from Slack
* The idea opened and the breadcrumb made it appear as though this idea came from the Archive but it is not archived. I had to do a double take to make sure i had not archived it accidentally

The way I see it is. If I want to send someone a view I will send the view.

If I want to send someone an idea, I only want to send the idea - I do not need or want any view information carried along with it.

Side note: I'm the guy who wrote the post you linked in your side note ha


author: Jan-Hendrik Spieth
body: Hi [@Ian Sperry](/t5/user/viewprofilepage/user-id/4559137), yeah I noticed it's you :-)

I believe you're right about a "permanent issues list". We have one view called "All ideas", basically a list without filters. I guess that comes close.

Your experience with ending up in the Archive is a good example of how the current behaviour can be confusing.

Currently, *a link to an idea in the form <https://you.atlassian.net/browse/ISSUE-KEY> takes the last visited view as context*.

[@Ben Arundel](/t5/user/viewprofilepage/user-id/5078714)if you haven't noticed this yet, give it a try - so you see the "nice" links already exist and they work, you just have to construct the URL manually, or let it be generated e.g. with the Jira macro in Confluence.

Not sure what happens for users who open JPD the first time, though :-)

Maybe I'm overthinking things, but when it comes to sharing, JPD views determine who has access, and how. And I believe that's a good feature.

So, what would the permissions for the "permanent issues list" look like? Maybe customizable, just like the other views? Of course that would mean that an idea link doesn't work for everyone.


author: Rohan Swami
body: Hi all, as you've identified the extra bits on the end of the URL dictate the view that the idea will be opened in. We'll look to improve the URLs at the some point, but it's not on our roadmap for now.

Personally, I agree with you that when sharing a link I want to take someone to see the idea and not the view. But this is a highly used feature so we'll want to do some careful research and testing before making a change here.