Atlassian Update - 06 May 2020

      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

      Atlassian Update - 29 April 2020

      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

      Atlassian Update - 24 March 2020

      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

      Atlassian Update - 11 Feb 2020

      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

      Atlassian Update - 10 Dec 2019

      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!

            [JRACLOUD-70156] Ability to link to a specific comment when using the new issue 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...

            Martin Dorey added a comment - 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...

            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.

            Mark Frederick added a comment - 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".

            Matthew Canham added a comment - 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.

            Adam Stevenson added a comment - 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.

            Thank you for this feature, it was very helpful.

            Mark Faderon added a comment - Thank you for this feature, it was very helpful.

            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.

            Karl Becker added a comment - 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.

            Zac Spitzer added a comment - here you go https://jira.atlassian.com/browse/JRACLOUD-73196

            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.

            Martin Dorey added a comment - 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.

            Adam Stevenson added a comment - 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

            Zac Spitzer added a comment - 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

              Unassigned Unassigned
              a547c97b8a48 janis_elmeris_magebit
              Votes:
              598 Vote for this issue
              Watchers:
              190 Start watching this issue

                Created:
                Updated:
                Resolved: