We're using JIRA 6.0.5. When I click the icon that says "A permanent link to a comment" that's displayed to the upper right of every comment I see this behavior (FF, Chrome and IE 10):

      1) My browser follows the link, showing the issue and highlighting the comment

      2) The URL shows the full link, but 200 msec later, the URL shortens to just show the issue ID.

      In previous versions (e.g. JIRA 5.1.8.) when I clicked the icon that says "A permanent link to a comment" JIRA created a permanent link to the comment, which included the comment id in the URL.

      I assume this is a kind of regression bug.

      Cheers
      Kai

      Parts of the description taken from atlassian answers

            [JRASERVER-34998] Permalink to comments do not work

            DelphyM added a comment -

            Thanks jcastro for your response.
            I have created a new support request for it with this number: JSP-266085
            I wasn't able to assign it or include you on the CC list unfortunately.

            Kind Regards,
            -d

            DelphyM added a comment - Thanks jcastro for your response. I have created a new support request for it with this number: JSP-266085 I wasn't able to assign it or include you on the CC list unfortunately. Kind Regards, -d

            dmladek874681981

            It sounds like you might be running into a known bug JRA-59746. If you would open a ticket with support.atlassian.com and ask for it to be assigned to me. We appreciate your feedback.

            Jose Castro (Inactive) added a comment - dmladek874681981 It sounds like you might be running into a known bug JRA-59746 . If you would open a ticket with support.atlassian.com and ask for it to be assigned to me. We appreciate your feedback.

            DelphyM added a comment -

            I actually think, this is a regression bug too and if it was desired change not to focus referenced comment than what is the point to linking comments at all?

            Some of our issues they have lot's of comments, and in such it is impossible to which comment someone else is referring to, also jumping on top of the Jira issue, is not very helpful.

            It used to behave well, but not anymore.

            DelphyM added a comment - I actually think, this is a regression bug too and if it was desired change not to focus referenced comment than what is the point to linking comments at all? Some of our issues they have lot's of comments, and in such it is impossible to which comment someone else is referring to, also jumping on top of the Jira issue, is not very helpful. It used to behave well, but not anymore.

            Max Paw added a comment -

            Bug is still real 7.1.1

            Max Paw added a comment - Bug is still real 7.1.1

            zorji added a comment -

            The issue 2) in description still exists, my JIRA version is JIRA v7.1.0-OD-01-053.
            The permalink only links to the ticket, but doesn't link to the comment.

            zorji added a comment - The issue 2) in description still exists, my JIRA version is JIRA v7.1.0-OD-01-053. The permalink only links to the ticket, but doesn't link to the comment.

            MattS added a comment -

            I think it's viewed as a feature

            MattS added a comment - I think it's viewed as a feature

            The bug also affects JIRA 6.2.6 (EAR/WAR)

            Corentin Bresson added a comment - The bug also affects JIRA 6.2.6 (EAR/WAR)

            MattS added a comment -

            I've updated the docs to reflect the new behavior

            MattS added a comment - I've updated the docs to reflect the new behavior

            Atlassian,

            looks like your documentation is wrong on this feature then. Please see: "Linking to a comment" at the bottom of https://confluence.atlassian.com/display/JIRA062/Commenting+on+an+Issue

            Dave Donnelly [Sensata] added a comment - Atlassian, looks like your documentation is wrong on this feature then. Please see: "Linking to a comment" at the bottom of https://confluence.atlassian.com/display/JIRA062/Commenting+on+an+Issue

            AgilePM added a comment -

            IMO this feature has been broken based on new functionality being implemented and either was not regression tested properly or the failure of that regression test was written off as acceptable. Not every user of JIRA will be able to perform the right click > copy link address. Also, how does this work for mobile users?

            AgilePM added a comment - IMO this feature has been broken based on new functionality being implemented and either was not regression tested properly or the failure of that regression test was written off as acceptable. Not every user of JIRA will be able to perform the right click > copy link address. Also, how does this work for mobile users?

            Alan Meyer added a comment -

            As a computer programmer, I understand that every feature has a cost, development organizations have just so much money they can spend, and it is essential to prioritize features. The solution that Atlassian has here seems to me not ideal, but it does meet the most important requirement - enabling someone to create a link to a comment.

            Right click copying of a URL seems okay to me. It's easy. The main downside seems to be that it's not obvious to the user what she has to do. Someone has to teach her or she has to find a manual, or do as I did, do a Google search. The obvious left click doesn't work and most users are likely to just give up, possibly with some muttered imprecations.

            One enhancement I'd like to see is a cleaner URL. Instead of:

            https://jira.atlassian.com/browse/JRA-34998?focusedCommentId=520644&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-520644

            How about something like: https://jira.atlassian.com/browse/JRA-34998?comment=520644

            I'm guessing that could be implemented and tested in less than a day's work.

            I don't know what the rest of the current URL does, but the string that says "com.atlassian.jira.plugin..." looks suspiciously like it could be an invocation of a specific Java class. If so, it might be an easy target for a hacker to substitute some other class identifier with a whole world of possible outcomes - not a good idea.

            Alan Meyer added a comment - As a computer programmer, I understand that every feature has a cost, development organizations have just so much money they can spend, and it is essential to prioritize features. The solution that Atlassian has here seems to me not ideal, but it does meet the most important requirement - enabling someone to create a link to a comment. Right click copying of a URL seems okay to me. It's easy. The main downside seems to be that it's not obvious to the user what she has to do. Someone has to teach her or she has to find a manual, or do as I did, do a Google search. The obvious left click doesn't work and most users are likely to just give up, possibly with some muttered imprecations. One enhancement I'd like to see is a cleaner URL. Instead of: https://jira.atlassian.com/browse/JRA-34998?focusedCommentId=520644&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-520644 How about something like: https://jira.atlassian.com/browse/JRA-34998?comment=520644 I'm guessing that could be implemented and tested in less than a day's work. I don't know what the rest of the current URL does, but the string that says "com.atlassian.jira.plugin..." looks suspiciously like it could be an invocation of a specific Java class. If so, it might be an easy target for a hacker to substitute some other class identifier with a whole world of possible outcomes - not a good idea.

            I agree with copying it to clipboard. After the URL initially disappeared I figured it was copied to the dashboard which is not the case. I am strongly against the suggestion to right click and copy the link address. What kind of experience is that??? ESPECIALLY since the rest of the adjacent icons do not work in that manner. Terrible.

            Deleted Account (Inactive) added a comment - I agree with copying it to clipboard. After the URL initially disappeared I figured it was copied to the dashboard which is not the case. I am strongly against the suggestion to right click and copy the link address. What kind of experience is that??? ESPECIALLY since the rest of the adjacent icons do not work in that manner. Terrible.

            @ Warren Racz : A very good suggestion !

            Chamara Hatharasinghe added a comment - @ Warren Racz : A very good suggestion !

            Warren added a comment -

            Would it make more sense to change the link behavior to a copy to clipboard function, and a message sating the link has been copied to the clipboard as an alternative.

            Warren added a comment - Would it make more sense to change the link behavior to a copy to clipboard function, and a message sating the link has been copied to the clipboard as an alternative.

            To make this "expected behavior" seems to be almost naive to me. A novice user may not even know about the existence of copy shortcut functionality, and to assume that they can intuit the steps needed to make that work isn't quite the best user experience to me. The page reloads and the comment is blue, and then to see that the URL is not correct (which they may not realize at all, in fact) is disappointing.
            "Won't Fix" would seem to be more representative of the product decision, especially if it is due to some kind of technical limitation.

            Deleted Account (Inactive) added a comment - To make this "expected behavior" seems to be almost naive to me. A novice user may not even know about the existence of copy shortcut functionality, and to assume that they can intuit the steps needed to make that work isn't quite the best user experience to me. The page reloads and the comment is blue, and then to see that the URL is not correct (which they may not realize at all, in fact) is disappointing. "Won't Fix" would seem to be more representative of the product decision, especially if it is due to some kind of technical limitation.

            LE MEE added a comment -

            We need a fix as fast as possible.
            Thank you

            LE MEE added a comment - We need a fix as fast as possible. Thank you

            Sadly I won't be making it along this time, I'm based in our Australian office and didn't submit a talk. Maybe next year
            Cheers,
            James

            James Hazelwood added a comment - Sadly I won't be making it along this time, I'm based in our Australian office and didn't submit a talk. Maybe next year Cheers, James

            Hi James,

            now that I know, that it is intended and the workaround is feasible it is absolutely acceptable. Thanks for the instant feedback. CU @ summit?!

            Cheers
            Kai

            Kai Gottschalk added a comment - Hi James, now that I know, that it is intended and the workaround is feasible it is absolutely acceptable. Thanks for the instant feedback. CU @ summit?! Cheers Kai

            Hi kai.gottschalk@xing.com,
            This is now expected behaviour, because of some extensive changes to how our issue navigator works with urls. Right clicking the permalink icon and selecting "copy link url" or similar will get you the permalink.
            I'm sorry if this breaks your standard workflow for working with permalinks, but hope the right click approach will do the trick.

            Regards,
            James Hazelwood
            Atlassian

            James Hazelwood added a comment - Hi kai.gottschalk@xing.com , This is now expected behaviour, because of some extensive changes to how our issue navigator works with urls. Right clicking the permalink icon and selecting "copy link url" or similar will get you the permalink. I'm sorry if this breaks your standard workflow for working with permalinks, but hope the right click approach will do the trick. Regards, James Hazelwood Atlassian

              Unassigned Unassigned
              4022a846e2fa Kai Gottschalk
              Affected customers:
              0 This affects my team
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: