Re: [platform-swt-dev] Using 'triaged'keywordinsteadofswt-triaged@xxxxxx

["Daniel Megert" <daniel_megert@xxxxxxxxxx>]

Keeping the bug status as NEW makes it
harder to find new untriaged bugs. One has to use a regex to exclude the
keyword.

> There is no
need to remove triaged keyword once added.
Yes, it should definitely be kept once
added.

Note that a bug can also be assigned
to a person but be in the NEW state. We have thousands of those. Many developers
take some bugs they plan to work on but only set ASSIGNED when they are
actually working on it.

What is the user-friendly query that
you are looking for?

Just to be clear: I am definitely for
getting rid of the additional *-triaged@xxxxxxxxxxx account, because having
two inboxes does make a search hard.

Dani



From:      
 Leo Ufimtsev <Leonidas@xxxxxxxxxx>
To:      
 "Eclipse Platform
SWT component developers list." <platform-swt-dev@xxxxxxxxxxx>
Date:      
 15.06.2017 20:56
Subject:    
   Re: [platform-swt-dev]
Using 'triaged'        keywordinsteadofswt-triaged@xxxxxxxxxxx?
Sent by:    
   platform-swt-dev-bounces@xxxxxxxxxxx

---

On Thu, Jun 15, 2017 at 10:58 AM, Daniel Megert <daniel_megert@xxxxxxxxxx>
wrote:
> There are already
600+ bugs with the "Triaged" keyword in the keyword list.
Please... In the Eclipse top-level project there are exactly 6 bugs with
that keyword and guess who has set it?

Searching "!Triaged":
https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=!triaged&list_id=16446297
Yields 676 bugs.
Again, I"m not introducing a new keyword to our Bugzilla
instance, but just suggesting to make use of what's already there.


> Can you explain
why you prefer to use "Assigned" status to mean triaged instead
of using the existing "Triaged" keyword? 
Because it's the process we use for over 15 years. 

"Assignee@Inbox AND status=ASSIGNED" was not
exclusively used for 15 years by all projects. At least in SWT, the process
has been to assign bugs to a "triaged-" and leave bugs as "NEW"
user.
Ex: SWT has 506 bugs assigned to " swt-triaged@xxxxxxxxxxx",
all of which have status=NEW. See
https://bugs.eclipse.org/bugs/buglist.cgi?quicksearch=%3Aswt%20%40triaged&list_id=16446333
Where as there are only 56 bugs on swt-platform-inbox
with status ASSIGNED. 

Also, it's worth mentioning that Gtk2 has been around
for 15 years. But now people are moving on to Gtk3. 

Further, if you look at the official Bugaillz wiki:
https://en.wikipedia.org/wiki/Bugzilla
"Assigned" status is only used when a developer
takes possession:


Other bugzilla instances follow this method. I think we
should too.

So we're actually miss-using ASSIGNED status if a developer
is not actually taking possession of a bug.


Because it's faster to just assign a
bug than fiddling with the keyword field.

Adding "Triaged" keyword requires 2 actions:
you to type "t" (or "tr") and select "Triaged"
from list:


There is no need to remove triaged keyword once added.
Setting Status to "Assigned" also requires 2
actions: Click on status -> assigned.
Keyword "triaged" can be added or removed in
bulk and Keywords can be shown in query results.
So I don't see a difference in usability besides a few
simple adjustments to one's workflow.

You could argue that it's marginally simpler to use "Assigned"
status for developers, but I think we should prioritize user friendliness
and global consistency over personal preference.

[attachment "Selection_474.png"
deleted by Daniel Megert/Zurich/IBM] [attachment "Selection_475.png"
deleted by Daniel Megert/Zurich/IBM] _______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev