JIRA
  1. JIRA
  2. JRA-28976

Provide a way to link a comment to another issue's comment

    Details

    • Type: Improvement Improvement
    • Status: Resolved (View Workflow)
    • Resolution: Won't Fix
    • Affects Version/s: 5.0.6
    • Fix Version/s: None
    • Component/s: Comments
    • Labels:
      None

      Description

      I've filed this issue as per https://answers.atlassian.com/questions/69998/how-to-insert-into-a-comment-a-link-to-a-certain-comment-of-another-issue-without-using-an-absolute-url
      Please note I don't want to establish a relationship between two issues... but simply refer to a certain comment (possibly on another issue within the same jira instance).
      A link using the comment sequence number would be great. I guess also something similar to confluence syntax [$comment-id] would be enough when you simply want to refer to what has been written into another issue's comment.
      Instead, having to provide an absolute URL is not portable at all.

        Issue Links

          Activity

          Hide
          John Gibson added a comment -

          This is a duplicate of an older feature request that was rejected at the time. Hopefully the developers will be interested in implementing it now, because I too would find it useful.

          Show
          John Gibson added a comment - This is a duplicate of an older feature request that was rejected at the time. Hopefully the developers will be interested in implementing it now, because I too would find it useful.
          Hide
          Roy Krishna [Atlassian] added a comment -

          Thanks for raising this again guys.

          However at this time we will not be implementing this request.

          Cheers,
          Roy

          Show
          Roy Krishna [Atlassian] added a comment - Thanks for raising this again guys. However at this time we will not be implementing this request. Cheers, Roy
          Hide
          Michael Bostwick added a comment -

          I wish on issues like this, you would leave it closed but allow users to votes, so that if an issue came up enough, you could consider it through other mechanisms..

          Show
          Michael Bostwick added a comment - I wish on issues like this, you would leave it closed but allow users to votes, so that if an issue came up enough, you could consider it through other mechanisms..
          Hide
          Alan Meyer added a comment -

          I'd vote for it if it were open and know former Bugzilla users at the organization where I'm using JIRA that I think would vote for it.

          I know that this has been rejected twice now, but no reason was given at either time. I'd be curious to know why. Is it too much work? Is it thought that there is insufficient demand to justify the work? Is it thought that the approach is wrong and that Permalinks are superior? Is it thought not to be useful?

          As a truly low cost alternative, I'd be in favor of simply attaching a counter to the identification line of a comment. For example,

          Instead of: "Alan Meyer added a comment - 27/Mar/14 11:45pm"
          Have:"Alan Meyer added comment_4- 27/Mar/14 11:45pm"

          The only cost is adding the comment counter "_4".

          The value of this is that a user could easily type "See comment_4-" in a reference to another comment and another user could use his browser's search feature (Ctrl-F) to quickly find it. I suggest "_4-" rather than "_4" so as to not have to deal with finding _4, _40, _41, _401, etc. However, a user could easily learn to search for "_4 " (space between '4' and '' if needed.

          If software may exist that depends on the existing string, add something separate before or after or on a different line, perhaps "cmt(4) or any other unique ID counter string.

          The comment number would just indicate that this is the fourth comment entered chronologically. If a site or user sorts comments differently, that's no big deal. A reference to, and search for, "comment_4-" or "cmt(4)" still works fine and is still semantically meaningful.

          Thanks.

          Show
          Alan Meyer added a comment - I'd vote for it if it were open and know former Bugzilla users at the organization where I'm using JIRA that I think would vote for it. I know that this has been rejected twice now, but no reason was given at either time. I'd be curious to know why. Is it too much work? Is it thought that there is insufficient demand to justify the work? Is it thought that the approach is wrong and that Permalinks are superior? Is it thought not to be useful? As a truly low cost alternative, I'd be in favor of simply attaching a counter to the identification line of a comment. For example, Instead of: "Alan Meyer added a comment - 27/Mar/14 11:45pm" Have:"Alan Meyer added comment_4- 27/Mar/14 11:45pm" The only cost is adding the comment counter "_4". The value of this is that a user could easily type "See comment_4-" in a reference to another comment and another user could use his browser's search feature (Ctrl-F) to quickly find it. I suggest "_4-" rather than "_4" so as to not have to deal with finding _4, _40, _41, _401, etc. However, a user could easily learn to search for "_4 " (space between '4' and ' ' if needed. If software may exist that depends on the existing string, add something separate before or after or on a different line, perhaps "cmt(4) or any other unique ID counter string. The comment number would just indicate that this is the fourth comment entered chronologically. If a site or user sorts comments differently, that's no big deal. A reference to, and search for, "comment_4-" or "cmt(4)" still works fine and is still semantically meaningful. Thanks.
          Hide
          Marc Guenther added a comment -

          I find it interesting that something as trivial and useful as this, is closed as rejected twice now, without giving any kind of explanation whatsoever, and not even letting people vote on it. So either Atlassian has no system for collecting feature requests from users (but they have, it's called Jira, it even supports voting...), or they simply don't care about their customers wishes...

          Pick your choice...

          Show
          Marc Guenther added a comment - I find it interesting that something as trivial and useful as this, is closed as rejected twice now, without giving any kind of explanation whatsoever, and not even letting people vote on it. So either Atlassian has no system for collecting feature requests from users (but they have, it's called Jira, it even supports voting...), or they simply don't care about their customers wishes... Pick your choice...

            People

            • Assignee:
              Unassigned
              Reporter:
              Davide Cavestro
            • Votes:
              3 Vote for this issue
              Watchers:
              9 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: