-
Sub-task
-
Resolution: Fixed
-
Highest
-
None
-
None
Hi Everyone,
I want to provide a quick update for this topic. we finished rolling out this feature and now it should be available for all Jira customers. Thank you very much and appreciate your patience on this.
Regards,
Atlassian
Hi Everyone,
I want to provide a quick update for this topic. we started rolling out this feature and should be available for all Jira customers in the following week. We understand this has taken a while to build out, but rebuilding Jira issues is no small feat, so we very much appreciate your patience on this.
Regards,
Atlassian
Hi Everyone,
I want to provide a quick update for this topic. The work is still in progress to ship this feature, Ability to link to a specific comment "Permalink", and aiming to roll it out in the next couple of weeks and it will include all the existing functionality that was on the old issue view. I know this has taken a while to build out, but rebuilding Jira issues is no small feat, so we very much appreciate your patience on this.
In the meantime, you can opt out of this new issue experience via your Personal Settings > Jira Labs section will have a 'new issue view' toggle to turn it on or off. We will not be disabling this opt-out option until we have rebuilt all the key features of the Jira issues experience you have come to know and love.
Regards,
Atlassian
Hi Everyone,
I want to provide a quick update for this topic. We started the work on this feature, Ability to link to a specific comment "Permalink", and aiming to roll it out in the next couple of weeks and it will include all the existing functionality that was on the old issue view. I know this has taken a while to build out, but rebuilding Jira issues is no small feat, so we very much appreciate your patience on this.
In the meantime, you can opt out of this new issue experience via your Personal Settings > Jira Labs section will have a 'new issue view' toggle to turn it on or off. We will not be disabling this opt-out option until we have rebuilt all the key features of the Jira issues experience you have come to know and love.
Regards,
Atlassian
Hi Everyone,
I want to provide a quick update for this topic. We are about to start the work on this feature, Ability to link to a specific comment "Permalink", and aiming to roll it out in the next couple of months and it will include all the existing functionality that was on the old issue view. I know this has taken a while to build out, but rebuilding Jira issues is no small feat, so we very much appreciate your patience on this.
In the meantime, you can opt out of this new issue experience via your Personal Settings > Jira Labs section will have a 'new issue view' toggle to turn it on or off. We will not be disabling this opt-out option until we have rebuilt all the key features of the Jira issues experience you have come to know and love.
Regards,
Atlassian
The permalink functionality – ability to link to a specific comment – has disappeared in the new issue view. Please, add the feature back!
- depended on by
-
JRACLOUD-71643 New issue view should appear when user gets a notification of being mentioned in a comment
-
- Closed
-
- is blocked by
-
JRACLOUD-74727 New issue view - link to a specific comment collapsed just opens the regular issue view, the comment is not focused.
-
- Closed
-
-
JRACLOUD-73196 Ability to expand the comment section at once in the new issue view - Expand all
- Gathering Interest
- is duplicated by
-
JRACLOUD-73636 Ability to copy link of comment in the New Issue View
-
- Closed
-
- relates to
-
BENTO-4300 Failed to load
Form Name |
---|
[JRACLOUD-70156] Ability to link to a specific comment when using the new issue view
It does not work right. If i paste a permalink to another ticket's specific comment into some other Jira ticket and later i click that link to go to that comment, the browser takes me to the correct ticket and maybe to the "general area" of the target comment, but does not land on the target comment. I have to copy the permalinks to comments in that area to Notepad to read the id of the target comment to find the right one.
Hi everyone, this ticket was mistakenly reopened. Closing again as "Fixed".
Actually, this is the bug people should follow and vote on:
https://jira.atlassian.com/browse/JRACLOUD-74727
The other one Zac posted is just a feature request to be able to auto-expand hidden comments but doesn't address linking to comments specifically.
Thanks for writing that bug up, vote submitted.
I understand the difficulty of writing front-end UI that accesses paging APIs, and how tricky that can be. But without Jira handling the paging properly to keep auto-expanding the comments until it finds the one specified in the URL, this JRACLOUD-70156 issue here is still very much unfinished in my mind.
I submitted a bug report to Atlassian on this.
We've been trying to summon up the willpower to do that for weeks now, so thank you. Please post the link so we can watch and vote for it.
This still doesn't work as the frustrating new "view 10 more comments" doesn't auto expand to the linked comment
Indeed. I noticed this yesterday. Seems like a bug to me. If a linked comment cannot expand hidden comments, it somewhat defeats the purpose of this feature improvement.
I submitted a bug report to Atlassian on this.
This still doesn't work as the frustrating new "view 10 more comments" doesn't auto expand to the linked comment
https://luceeserver.atlassian.net/browse/LDEV-1933?focusedCommentId=42296
Glad to have this feature back.
I see it now in my company's Jira Cloud instance.
I'm very happy to see this start getting implemented!
I just noticed it today in my company's Jira Cloud instance.
I think what frustrates people more than the huge delay in bringing this back, is that such a useful feature that already existed was taken away in the first place.
Perhaps next time elements of the product that we pay for each month are being removed - wider consultation on the impact could take place ahead of time?
Thanks
Hooray! Excited to have this get released soon - I see the little link icons beside comments here!
Although, now I'm curious: why doesn't this copy of Jira use the new comment submitting GUI that is in my cloud copy of Jira? The editing text box is definitely a different style... it looks like the version here is older.
Are the little link icons I see on this Jira actually from an older version of Jira?
+1 Since Feb the feature has been "aiming to roll it out in the next couple of weeks". I think going forward it far easier for everyone not to remove features when you do an upgrade.
I thought it was user error on my side that I wasn't finding this option (as a new Jira user)... this is how basic, and essential it is.
Crazy that this hasn't been done yet!
+1
to the return of the permalink functionality for comments
I really don't understand why Jira Cloud and Confluence Cloud are so much worse in terms of functionality then the normal on-premise versions.
Altassian, please use the old, good version for cloud versions.
If you add ?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel to your issue URL, you'll be able to get to the comment permalink.
+1 First raised 2018 and estimated to take a couple of months before release.
Do enjoy using Jira but for future upgrades, please don't remove useful features.
I'm subscribed to receive updates about feature development.
Please stop adding generic "+1" comments every week. It's already a long thread, so it won't help with anything.
Sorry for contributing to this spam, but hope it will reduce comments like this.
This is still not implemented? 😳we're waiting more than a year now....
I'm pretty shocked that the new UI was pushed so hard, and pretty much become the default, with this linking mechanism killed
And in fact, I see now that this very jira.atlassian.com site does NOT use the new UI - perhaps that says it all 😬
Thank you for the update on Dec 10 at least. But I sure hope "the next couple of months" gets a tighter time frame soon - how about "sometime in February"? Or at least "Quarter 1 2020" to give us a rough idea?
Thanks!
Was anybody asked if they'd finished with the massively useful permalink feature and it could be taken away with the "new look Jira" ? I don't remember being asked and it's a real pain not having it.
I can't believe linking to comments used to be a feature... and was removed? I'm convinced that Jira developers don't know they aren't the only ones using Jira (then again, I'm sure they just use Trello so they don't care if they mess up Jira).
I'm now adding this to the ever-growing list of reasons why my company should ditch Jira and use something - anything - else.
Atlassian. Please. We need this. Paper trails are a tad pointless if you can't link directly.
Indeed this seems to be one of those cases when it's difficult to get an actual update on the issue (status = in progress // assignee = unassigned).
Would there be any info on which release could re-embed this feature? If still available on the classic view I'd believe the permalink is still present in the code, just removed from the mark up of the page?
Thanks in any case,
A.
Seems worth pointing out that though there has not been a response in the comments from Atlassian, this issue did move to "In Progress" on August 19th. Yes, it's been nearly 3 months since then, but there's reason to think that they are working on this and not just ignoring the plethora of comments here.
Hard to believe this request started on 03/Sep/2018. And not a single reply back from the team of acknowledgement despite nearly so many comments
+10000000000
Are there any updates on this feature? Seems fairly simple to implement. Cannot believe it doesn't exist in the new issue view.
A sub-task open since September 2018. In my company this would mean this is 'never-to-be-done' stuff. Shame.
+1 along with EVERYBODY ELSE, because holy smokes the ball got dropped on this feature
ahah - I don't understand why do I need switching between comment date and it's age at all comparing to the comment link.
October 17, 2019, 7:30 PM vs 9 minutes ago
Does anybody use it in new UI? Keep it up!
+1
and ideally there would be a user-friendly way to refer to comments besides the permalink, such as a simple numbering of the comments (1, 2, 3, 4, ...)
+1
There are only two reasons I still have to return to the old view: comment linking and adding a link to a web resource (as opposed to another ticket or confluence).
Given the history of this ticket, the plethora of negative reaction we've all had and the total lack of any commitment or response from Atlassian, it's pretty clear they truly place little to no value on change control, customer satisfaction, product reputation nor their paying clientele.
I hope they don't over-analyse too much when they see cohorts of long term users convert to other offerings as that would truly be a waste of resources and energy..
+1
I'm shocked that this was either removed from the product, or released broken.
+1
Could live without icons, but not without permalink to comments on long issues with a lot of interactions - please bring the permalink to a comment back
It would be nice to be able to auto-link to another issue's comment like "JRACLOUD-70156 comment 2282057" would link to the specified comment in the specified issue. Auto-linking to specific comments is a feature in, for example, Bugzilla.
@Sonia
>Implementing likes, and dropping the permalinks .....this software is not used usually by teens, have that in mind.
I started management by emoji
@Sonia,
Once I pictured using Jira as a "family management project" , implementing some nice workflow with it, Pending weekend trip, Awaiting son/daughter's response, Resolved by lovely wife. Mind I don't have a family, yet... but yeah a fix for this would be useful I agree.
+1 for bring it back!
Implementing likes, and dropping the permalinks .....this software is not used usually by teens, have that in mind.
what Tara L Conkin said. My Team does not and cannot use the New View.
We simply cannot communicate with our Clients without the ability to link to a specific comments.
As of this comment the status shows "in progress" and the "updated" field says "3 hours ago". Let's hope this means Atlassian is working on this and a resolution is soon to follow. I have many co-workers who refuse to use the New Issues View because of the missing comment permalinks.
Hopefully the transition of this ticket to "In Progress" is an indicator of forward momentum, though it doesn't appear assigned yet.
Thanks in advance, Atlassian, for prioritizing this customer requested feature.
(NOTE: I don't have any knowledge other than this ticket metadata to indicate hopeful progress)
Greatest irony: this very issue still retains comment linking, despite it having been stripped out of the version of Cloud pushed to all customers.
Atlassian folks, some response would be really fantastic - as Jaspaul wrote, this has been open since last year. I posted over a month ago, and many other people have chimed in since. It looks like it's currently #36 on the priority board for Cloud, but considering that none of the other higher-priority items are reimplementations of stripped features, it should merit a response.
Please make this higher priority. I can see this is still open since Sept 2018
In my opinion, the main point of an issue tracker is to have all the information and communication about a task in one place, so that I can reference it whenever needed. Comments without permalinks are a similar mess as communicating everything via e-mail. Please bring this essential feature back.
The mind boggles why useful existing functions aren't implemented at GoLive... +1 of course to have this added back in asap.. Thank you Atlassian Team!
Please do not remove the "old" issue view without first adding this indispensable feature to the "new" view!
How sneaky, the feature was quietly removed. Why to push for the new UI if its incomplete?!
Thanks @Alexey Petinov for the clarification about using "Old (issue) view" rather than an "All view."
I'm happy to have the ability to link, even if it doesn't work perfectly every time, so am happy to call this Closed, but, if there's a new bug for the issue described by @MarkFrederick, then I'd like to watch and vote on that too. I don't think it's as cut-and-dried for me. I'm pretty sure I've seen it work well, but I've got an example in front of me right now (which I hope no one else can see but, for my future reference, is https://insightgroup.atlassian.net/browse/UDOP-1811?focusedCommentId=319841) where it will not scroll to the right place. If I refresh, it doesn't move. If I scroll down, then I see a handful of other comments with the default white background, then one with a gray background. Ooh, what's that? Ah, it's the one that's supposed to be focused. It's hard to tell it's the right one, because hovering over the link just offers the tooltip "Copy link to comment" rather than showing me what it links to, so I could compare it with the address bar. But I've double-checked and it's the right one. Hit refresh and I'm back to the wrong comment. I mean, it's alright when I'm linking for my own benefit, but...