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

Link to HipChat room from JIRA issue description

XMLWordPrintable

      NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.

      When I try to link to a HipChat room in the description of a JIRA issue, the link points to the wiki instead. For example,

      JIRA markup
      Notify members of [My Room|hipchat://mycorp.hipchat.com/room/484175] when ready.
      Rendered link
      <a href="https://mycorp.jira.com/wiki/display/hipchat/%2F%2Fmycorp.hipchat.com%2Froom%2F484175" title="Follow link">My Room</a>

            [JRASERVER-43301] Link to HipChat room from JIRA issue description

            Ewelina Fiedorowicz added a comment -
            Atlassian Update – 22.07.2021

            Hi Everyone,

            We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out.

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,
            Ewelina Fiedorowicz

            Ewelina Fiedorowicz added a comment - Atlassian Update – 22.07.2021 Hi Everyone, We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Time Out . Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Jira team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Ewelina Fiedorowicz

            Oswaldo Hernandez (Inactive) added a comment -

            True jdevenny,

            I missed that on my first read. Let's fix that first, maybe it's all that we actually need to do.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - True jdevenny , I missed that on my first read. Let's fix that first, maybe it's all that we actually need to do. Cheers, Os.

            Josh Devenny added a comment -

            Sounds like a bug on the JIRA side to me ohernandez@atlassian.com - seems like it's got something to do with the base URL of the instance? It's appending the Confluence /wiki/display URL to the beginning of the hipchat:// URL. Maybe all that's required here is for JIRA to recognise that hipchat:// is a valid URL protocol.

            Josh Devenny added a comment - Sounds like a bug on the JIRA side to me ohernandez@atlassian.com - seems like it's got something to do with the base URL of the instance? It's appending the Confluence /wiki/display URL to the beginning of the hipchat:// URL. Maybe all that's required here is for JIRA to recognise that hipchat:// is a valid URL protocol.

              Unassigned Unassigned
              276285cc5736 cbandy
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: