You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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:
And this is from the address bar:
It would be great to have nicely formatted URLs
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.
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:
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)?
I think JPD just needs a permanent Issues list to open in. I just had a situation in which this happened
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
Hi @Ian Sperry, 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 Arundelif 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.
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.