Bug 191175

Summary: "Needs Triage" status must be valid only for default assignees
Product: Services Reporter: John Marino <marino>
Component: Bug TrackerAssignee: Marcus von Appen <mva>
Status: Closed Overcome By Events    
Severity: Affects Many People CC: mva
Priority: ---    
Version: unspecified   
Hardware: Any   
OS: Any   
Bug Depends on: 190518    
Bug Blocks:    

Description John Marino freebsd_committer freebsd_triage 2014-06-19 06:43:17 UTC 
At least to me, the status of "Needs Triage" makes no sense if the PR is assigned.   The mere act of assigning the PR to a specific person satisfies the triage.

However, many people "take" the PR without changing the status.  It's easy to do.

So there needs to be some kind of logic that checks this for validity or else just change the status automatically to "open".

I guess there is more than one value for default:
freebsd-bugs@
freebsd-ports-bugs@
freebsd-doc-bugs@

at least

I have other issues with the bug workflow, but this one looks like it needs to modify bugzilla.
Comment 1 John Marino freebsd_committer freebsd_triage 2014-06-19 06:44:01 UTC 
Add Eitan to CC list.
Comment 2 Eitan Adler freebsd_committer freebsd_triage 2014-06-19 07:01:26 UTC 
I agree.

Can you help with writing the perl code to check for this?  We still need to work out the deployment issues but the relevant bug should be fixed shortly.
Comment 3 John Marino freebsd_committer freebsd_triage 2014-06-19 10:16:21 UTC 
while I have reasonable (but rusty) perl skills, I don't know anything about bugzilla's internals.  For example, I don't know where the code would go, what is available to the scripts, if it's a plugin, etc.

I could probably review someone else's code...
Comment 4 John Marino freebsd_committer freebsd_triage 2014-06-26 10:49:56 UTC 
So what is the way forward to move this PR along?
Comment 5 John Marino freebsd_committer freebsd_triage 2014-07-10 16:02:47 UTC 
(In reply to Eitan Adler from comment #2)
> I agree.
> 
> Can you help with writing the perl code to check for this?  We still need to
> work out the deployment issues but the relevant bug should be fixed shortly.

Has there been any progress?
What can I do to help?
Comment 6 Marcus von Appen freebsd_committer freebsd_triage 2014-08-19 19:47:55 UTC 
I'll take it.

Just to clarify things about the workflow:

If the issue is taken (condition logged in user == new assigned to), the status has to be changed from "Needs Triage" to "Open", if not explicitly set by the user, correct?

What should happen, if the issue is assigned to a different user (logged in user != new assigned to). It also should be set to "Open" in my opinion.
Comment 7 Marcus von Appen freebsd_committer freebsd_triage 2014-12-14 20:16:40 UTC 
Since the status model has been overhauled. Bugs are "New" (formerly "Needs Triage") for as long as it needs for an assignee to evaluate, if they valid or not.
Thus, a bug does not necessarily have to be "New" only for the default assignee.