Details
-
Suggestion
-
Resolution: Unresolved
-
Browser access from all supported platforms
-
3
-
16
-
Description
NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
Problem Definition
The markdown renderer that Jira Cloud uses only recognizes HTTP-based URL's and URI's. Trying to embed links using other protocols, such as smb, file, or doors, Jira's markdown renderer fails to recognize them as legit hyperlinks.
Suggested Solution
Support links to other resources that use non http/https protocols
Why this is important
This is particular important for teams that have existing internal network storage, and don't want to duplicate where those files are stored by copying them to Jira's attachments. In many cases it would be very helpful for end users that can see a Jira issue, or a JSD request to be able to see links to internal resources in some scenarios.
Workaround
There are no work-around for this in Jira Cloud at this time. Should one become available this section will be updated to reflect this.
Attachments
Issue Links
- is duplicated by
-
JRACLOUD-43665 External links with application protocol don't work
- Closed
- is related to
-
JRACLOUD-82508 Ability to configure text-to-hyperlink behaviour so that only a url with scheme converts to a hyperlink
- Gathering Interest
-
JRASERVER-26419 Non-HTTP links are not recognized as Links in the markup language
- Gathering Interest
- relates to
-
JRACLOUD-76802 In the new issue view, in a multi-line text custom field or in the issue description field, not all the URLs are rendered as links
- Gathering Impact