Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-34998

Permalink to comments do not work

XMLWordPrintable

      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

            Bugfix Automation Bot made changes -
            Minimum Version New: 6
            Owen made changes -
            Workflow Original: JAC Bug Workflow v2 [ 2847061 ] New: JAC Bug Workflow v3 [ 2928847 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2587859 ] New: JAC Bug Workflow v2 [ 2847061 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - Restricted [ 1542633 ] New: JIRA Bug Workflow w Kanban v7 - Restricted [ 2587859 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels New: affects-server
            Hannes Obweger (Inactive) made changes -
            Component/s Original: View Issue [Deprecated] [ 25490 ]
            Owen made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 676304 ] New: JIRA Bug Workflow w Kanban v6 - Restricted [ 1542633 ]

            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

            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.

            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.

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

                Created:
                Updated:
                Resolved: