View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0020503||mantisbt||bugtracker||public||2016-01-11 18:48||2018-08-15 01:54|
|Target Version||Fixed in Version|
|Summary||0020503: Consider not expanding issues and notes internal links in some places|
When using the # character with a number, it automatically (if the number is an existing bug_id) expand to an url that point tho that issue number (also for comments)
While it's a useful feature, there are some places where they probably should not be expanded, for a better presentation.
|Tags||No tags attached.|
For the summary field, I don't think there is a reason to assume that such bug links are not valid. For the email representation, I think the HTML emails will make it look natural.
There will be cases where there is a body of an issue that has an error code number with the # prefix. This is likely to happen in the description or additional info, etc. The only case is to change the bug number prefix. Even escaping doesn't necessarily work, if these bugs are auto-logged or are a copy and paste of a big error message.
Note sure about the cases for history that you have in mind.
it came by looking at this issue history: 0020479
Let's see this way: I'm not saying that using URL in the summary text is invalid.
So, my thinking may lead to needing an additional "context" to use with the formatting plugin, which should be specified by the caller. And based of that context, parametrize whether translate urls or not.
The same problem occurs on the bug view page with an email address as summary. This produces invalid HTML code:
|2016-01-11 18:48||cproensa||New Issue|
|2016-01-12 01:52||atrol||Relationship added||related to 0011763|
|2016-01-15 04:24||vboctor||Note Added: 0052317|
|2016-01-15 05:32||cproensa||Note Added: 0052319|
|2016-01-15 05:41||cproensa||Note Added: 0052320|
|2018-08-15 01:54||jes||Note Added: 0060433|
|2018-08-15 01:54||jes||Note Edited: 0060433||View Revisions|