You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When showing an issue in the console, the raw text is shown including markup characters.
Since the markup is minimally invasive, this isn't an issue most of the time. With URL's however, this can pose a bit of an issue.
In the raw text, a URL is represented by the markup [link text|URL]. When link text is not explicitly set by the user, the link text is the same as the URL, resulting in [URL|URL]. For example:
[http://example.org/foo|http://example.org/foo]
My console sees this as the URL http://example.org/foo|http://example.org/foo and sends my browser to a non-existing page.
It would be nice if jira-cli could pre-process the markup language and render a console friendly representation.
Note: when the user sets a link text that doesn't look like a URL, this markup doesn't cause an issue.
[Example|http://example.org/foo]
My console correctly sends me to http://example.org/foo when clicking the link.
The text was updated successfully, but these errors were encountered:
When showing an issue in the console, the raw text is shown including markup characters.
Since the markup is minimally invasive, this isn't an issue most of the time. With URL's however, this can pose a bit of an issue.
In the raw text, a URL is represented by the markup
[link text|URL]
. Whenlink text
is not explicitly set by the user, thelink text
is the same as the URL, resulting in[URL|URL]
. For example:My console sees this as the URL
http://example.org/foo|http://example.org/foo
and sends my browser to a non-existing page.It would be nice if jira-cli could pre-process the markup language and render a console friendly representation.
Note: when the user sets a
link text
that doesn't look like a URL, this markup doesn't cause an issue.My console correctly sends me to
http://example.org/foo
when clicking the link.The text was updated successfully, but these errors were encountered: