Bug 409930

Summary:	Please automatically link to clear mentions of a given ticket ("ticket #12345")
Product:	[Websites] bugs.kde.org	Reporter:	Philippe Cloutier <chealer>
Component:	general	Assignee:	KDE sysadmins <sysadmin>
Status:	CLOSED MOVED
Severity:	wishlist	CC:	bcooksley, kde, sheedy
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Other
OS:	All
URL:	https://bugs.kde.org/show_bug.cgi?id=409913#c1
See Also:	https://bugs.kde.org/show_bug.cgi?id=410831 https://bugs.kde.org/show_bug.cgi?id=410832
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Philippe Cloutier 2019-07-18 04:51:52 UTC

It would be very handy if, when a description or comment referred to a ticket using unambiguous phrasing such as "ticket #123456" or "issue #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 comments, as can be seen in ticket #409913's comment #1, but not for tickets, as that same comment shows.

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.

Comment 1 Ben Cooksley 2019-07-18 07:37:11 UTC

Please note that entries in bugs.kde.org are bugs, not tickets.

Within a KDE context the term ticket usually refers to a Sysadmin Ticket (which are managed separately and not held on bugs.kde.org)

Comment 2 Kai Uwe Broulik 2019-07-18 07:41:00 UTC

Just write Bug 409913 which is linked properly.

Comment 3 Ben Cooksley 2019-07-18 07:43:45 UTC

Given that the correct syntax is automatically linked, I don't think there is anything to action here (and we don't want to confuse the terms task/ticket/bug, they are all used to refer to different things)

Comment 4 Christoph Feck 2019-07-18 12:39:02 UTC

You can also write bug 165044 comment #173 and it will be automatically linked to the specified comment.

Comment 5 Philippe Cloutier 2019-07-21 19:39:51 UTC

Thanks Ben,

(In reply to Ben Cooksley from comment #1)
> Please note that entries in bugs.kde.org are bugs, not tickets.

Entries are not bugs, but are you:
1. saying that entries are *called* "bugs"
2. unaware that some entries are not bug reports
3. or opining that all entries *should* be bug reports?
 
> Within a KDE context the term ticket usually refers to a Sysadmin Ticket
> (which are managed separately and not held on bugs.kde.org)

I see, you must be referring to https://phabricator.kde.org/maniphest/
I also see that the canonical term for these is "task". I will file different tickets for different terms.

Comment 6 Philippe Cloutier 2019-07-21 19:48:11 UTC

(In reply to Ben Cooksley from comment #3)
> Given that the correct syntax is automatically linked, I don't think there
> is anything to action here (and we don't want to confuse the terms
> task/ticket/bug, they are all used to refer to different things)

I agree there is a difference between "task" and "ticket", but given your above comment, please clarify what difference you see between these.

Comment 7 Philippe Cloutier 2019-07-27 16:09:28 UTC

Before opening new tickets, I will wait for bug #410284 to be solved (or at least a decision taken).

Comment 8 Philippe Cloutier 2019-08-12 00:40:19 UTC

Per comment #7, following ticket #410284's comment #1, I filed 2 separate tickets to replace this one:
Please automatically link on a ticket mention in the form "ticket #123456": https://bugs.kde.org/show_bug.cgi?id=410831
Please automatically link on a ticket mention in the form "issue [report] [#]123456": https://bugs.kde.org/show_bug.cgi?id=410832

Comment 9 Philippe Cloutier 2019-08-12 02:26:14 UTC

This ticket's status should be set to CLOSED MOVED, but as reported in ticket #410833, I cannot change it at this time.