Uploaded image for project: 'JIRA (including JIRA Core)'
  1. JIRA (including JIRA Core)
  2. JRA-19537

Easy way of linking from one comment to another

    Details

    • Type: Suggestion
    • Status: Closed (View Workflow)
    • Resolution: Answered
    • Affects Version/s: 4.0
    • Fix Version/s: None
    • Component/s: Comments
    • Labels:
      None
    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      Our team recently migrated from Bugzilla to JIRA and now we are missing a nice little feature of our bugzilla clunker.

      When writing a comment on an issue in Bugzilla it is possible to refer to another issue or even to a specific comment of another issue or to a another comment of the same issue by writing:

      There is something remarkable in bug1234comment2 to consider...

      This becomes ("There is something remarkable in bug1234comment2 to consider...") a link to comment #2 of ticket 1234.

      Or even shorter:

      ...as said in comment3 we have to...

      This becomes ("...as said in comment3 we have to...") a link to comment #3 of the same ticket as the new comment.

      One part of this feature is already available, JIRA does create links when it detectes a issue key within a comment. But for linking to another comment i have to use a cumbersome 'Permalink'.

      It is a little bit hard to explain the usage of permalinks to the users when they are used to the easy way of linking offered by Bugzilla. I (as JIRA admin) had been asked to add comment numbers to all comments so it would be possible to refer to other comments by their number.

        Attachments

          Issue Links

            Activity

            Hide
            nofel Sara Nofeliyan added a comment -

            can this be reopened?

            Show
            nofel Sara Nofeliyan added a comment - can this be reopened?
            Hide
            christer007 Christer Damm added a comment -

            Another vote for comment... well the previous comment.

            Show
            christer007 Christer Damm added a comment - Another vote for comment... well the previous comment.
            Hide
            nofel Sara Nofeliyan added a comment -

            Christer Damm I found a way to use threaded comments, Project>>Administration>>Fields>>Edit Fields>>Comments>>select "Wiki Style Renderer"

            Show
            nofel Sara Nofeliyan added a comment - Christer Damm I found a way to use threaded comments, Project>>Administration>>Fields>>Edit Fields>>Comments>>select "Wiki Style Renderer"
            Hide
            konqi Marcel "childno͡.de" Trautwein added a comment -

            Sara Nofeliyan it is not a question of a wiki-style-renderer and this neither enables "Threaded comments" neither the asked "linking to comments"

            @all: only workaround: use wiki styled renderer and advice users to clumsy add a "link" maually

            • copy the url of the comment (by hovering over the upper right of an comment, a link icon is shown
            • you might also dragn'drop it into the new comment text-box or paste the url
            • you'll get something like
              https://jira.atlassian.com/browse/JRA-19537?focusedCommentId=687549&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
            • make it short
              #comment-687549
            • wrap it with brackets
              [#comment-687549]

              here you are comment-687549 but it neither focus it correctly nor you'll get a focus highlight, better to just leave the cluttering long url ;( It's just ... crap and it's a pain atlassian continously closes these issues and we're forced to reopen them or even have to count further bugs on it ;( : JRA-37371

            it's even more getting strange reading CONF-27807 which reads like "they are discontinuing comment links in general ... w00t

            But: I'm hoping threaded comments JRA-3406 will be integrated in a forseenable future and will not die in the labs, if this would be a core feature, linking to comments might be obsolete because most use cases are then covered by threads

            Show
            konqi Marcel "childno͡.de" Trautwein added a comment - Sara Nofeliyan it is not a question of a wiki-style-renderer and this neither enables "Threaded comments" neither the asked "linking to comments" @all: only workaround: use wiki styled renderer and advice users to clumsy add a "link" maually copy the url of the comment (by hovering over the upper right of an comment, a link icon is shown you might also dragn'drop it into the new comment text-box or paste the url you'll get something like https: //jira.atlassian.com/browse/JRA-19537?focusedCommentId=687549&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel make it short #comment-687549 wrap it with brackets [#comment-687549] here you are comment-687549 but it neither focus it correctly nor you'll get a focus highlight, better to just leave the cluttering long url ;( It's just ... crap and it's a pain atlassian continously closes these issues and we're forced to reopen them or even have to count further bugs on it ;( : JRA-37371 it's even more getting strange reading CONF-27807 which reads like "they are discontinuing comment links in general ... w00t But: I'm hoping threaded comments JRA-3406 will be integrated in a forseenable future and will not die in the labs, if this would be a core feature, linking to comments might be obsolete because most use cases are then covered by threads
            Hide
            rousskov Alex Rousskov added a comment -

            we do not intend on implementing this in the foreseeable future.

            @rkrishna, it may help your users to know why Atlassian does not intend to implement something they want. Do they want the wrong thing? Does Atlassian plan on implementing something better? Does Atlassian agree this is a useful feature but needs to implement more useful features first? You have already upset your users by rejecting their request. Sweeten their defeat with justifying or explaining your rejection.

            I'll close this in the mean time to keep things tidy on our end.

            Thank you for keeping things tidy on your end! What do you suggest your users do on their end? Open yet another issue requesting the same feature? Log +1 comments here to express their interest while nobody on your end is listening (and everybody on this end gets annoyed by a yet another +1 comment)?

            If closing feature requests like that is your own idea, please discuss your approach with others at Atlassian: Is there a better way to tidy things up? If it is your management requirement, what do you suggest the folks on this end do to encourage your management to change their approach?

            If we ever look into your request again I'll be sure to reopen this issue.

            How would Atlassian know that they should look into this again if you do not let your users vote for this feature?

            And what if you are not around when Atlassian miraculously looks into this again? Who would advocate for your users then? I doubt this closed issue would!

            @konqi, thank you for a nice workaround! Unfortunately, it does not work for linking to comments in other issues. And adding support for threaded comments would not address that other-issue use case either. IMO, an ability to link to a comment in another issue is even more important than the ability to link to a comment in the same issue because you can not even say something like "look two comments above" when you are dealing with another issue.

            Show
            rousskov Alex Rousskov added a comment - we do not intend on implementing this in the foreseeable future. @rkrishna, it may help your users to know why Atlassian does not intend to implement something they want. Do they want the wrong thing? Does Atlassian plan on implementing something better? Does Atlassian agree this is a useful feature but needs to implement more useful features first? You have already upset your users by rejecting their request. Sweeten their defeat with justifying or explaining your rejection. I'll close this in the mean time to keep things tidy on our end. Thank you for keeping things tidy on your end! What do you suggest your users do on their end? Open yet another issue requesting the same feature? Log +1 comments here to express their interest while nobody on your end is listening (and everybody on this end gets annoyed by a yet another +1 comment)? If closing feature requests like that is your own idea, please discuss your approach with others at Atlassian: Is there a better way to tidy things up? If it is your management requirement, what do you suggest the folks on this end do to encourage your management to change their approach? If we ever look into your request again I'll be sure to reopen this issue. How would Atlassian know that they should look into this again if you do not let your users vote for this feature? And what if you are not around when Atlassian miraculously looks into this again? Who would advocate for your users then? I doubt this closed issue would! @konqi, thank you for a nice workaround! Unfortunately, it does not work for linking to comments in other issues. And adding support for threaded comments would not address that other-issue use case either. IMO, an ability to link to a comment in another issue is even more important than the ability to link to a comment in the same issue because you can not even say something like "look two comments above" when you are dealing with another issue.

              People

              • Assignee:
                Unassigned
                Reporter:
                atlassian@scheibler-family.de Maik Scheibler
              • Votes:
                4 Vote for this issue
                Watchers:
                21 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: