[kde] [Bug 410832] New: Please automatically link to mentions of a given ticket in the form "issue [report] [#]123456"

[Filipus Klutiero]

https://bugs.kde.org/show_bug.cgi?id=410832

            Bug ID: 410832
           Summary: Please automatically link to mentions of a given
                    ticket in the form "issue [report] [#]123456"
           Product: kde
           Version: unspecified
          Platform: Other
               URL: https://bugs.kde.org/show_bug.cgi?id=409912
                OS: All
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: chealer at gmail.com
  Target Milestone: ---

I am filing this ticket despite https://bugs.kde.org/show_bug.cgi?id=410284
with the assumption that its comment #1 is correct.

I put this ticket in the "general" component, but I suppose nothing prevents
addressing this with a code customization... please feel free to change the
component as you wish.

As discussed in https://bugs.kde.org/show_bug.cgi?id=409930 it would be very
handy if, when a description or comment referred to a ticket using phrasing
with low ambiguity like "issue #123456" or "issue report 123456", that this
text be automatically made a link to the ticket mentioned
(https://bugs.kde.org/show_bug.cgi?id=123456).

This already works for bugs, as can be seen in ticket #409930 comment #2, but
only when using the misleading form "bug #123456", and not for other issues or
when using general terminology, as ticket #409912's Description and comment #1
show.

Sometimes, a ticket may report several issues, or sub-issues. A description may
therefore list a number of issues, as in the following:
1. "Issue #123456" is not supported.
2. "Issue report #123456" is not supported.

Such a ticket may later refer to these "sub-issues" as "issue #1" (or "issue
#2"), which does not designate https://bugs.kde.org/show_bug.cgi?id=1, but
rather the first "sub-issue" reported in the current ticket.

To prevent generation of bogus links in such cases, it would be best to:
A. require at least 2 digits in the ticket number
B. or/and provide a syntax to disable automatic linking, such as
"~no-parse~issue #1~/no-parse~".

A KDE ticket may also refer to an issue in non-KDE software, for example the
X.org issue which has ticket number 12345. To prevent a sentence which contains
something like "this is blocked by X.org issue #12345" from generating a bogus
link to KDE's ticket #12345, a syntax to disable automatic linking like the one
just discussed (in point B) could be provided.

-- 
You are receiving this mail because:
You are the assignee for the bug.