Bug 1329480

Summary:	Please remove the button Start Working
Product:	[Community] Bugzilla	Reporter:	Rony Gong 🔥 <qgong>
Component:	Bugzilla General	Assignee:	PnT DevOps Devs <hss-ied-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	5.0	CC:	huiwang, jmcdonal, mtahir, qgong
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-12 23:55:08 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Rony Gong 🔥 2016-04-22 03:45:53 UTC

Description of problem:
Please remove the button Start Working

Everybody can click the button 'Start Working' once they can access bug and edit bug. In this case, I am sure that somebody will click the 'Start Working' accidentally and assign himself/herself as bug assignee. 

Two suggestions for this:
1.Remove this button 
2.Only the bug's assign could view and click this button 

Version-Release number of selected component (if applicable):
5.0.2-rh4

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Jeff Fearn 🐞 2016-04-26 06:11:00 UTC

hmm I could have sworn I replied to this.

This button is awesome!

The button is supposed to:

1: Only appear when the bug is in NEW state.
2: Only appear to people who have edit permission on the bug.
3: When clicked set the user as assigned and the status to ASSIGNED.

If any of these aren't happening then they are bugs.

Will not remove as it's been awesome in my testing.

Did I mention, it is awesome?

Comment 2 Rony Gong 🔥 2016-04-26 06:37:39 UTC

(In reply to Jeff Fearn from comment #1)
> hmm I could have sworn I replied to this.
> 
> This button is awesome!
> 
> The button is supposed to:
> 
> 1: Only appear when the bug is in NEW state.

No, After change the bug from New to Post, this button keep existing.

> 2: Only appear to people who have edit permission on the bug.

Yes

> 3: When clicked set the user as assigned and the status to ASSIGNED.

Indeed, It will set the user to assigned, but will not set the status to ASSIGNED in the case that this bug's already get changed in the before.

> 
> If any of these aren't happening then they are bugs.
> 
> Will not remove as it's been awesome in my testing.
> 
> Did I mention, it is awesome?

Comment 3 Jeff Fearn 🐞 2016-04-26 23:06:09 UTC

(In reply to Rony Gong from comment #2)
> (In reply to Jeff Fearn from comment #1)
> > hmm I could have sworn I replied to this.
> > 
> > This button is awesome!
> > 
> > The button is supposed to:
> > 
> > 1: Only appear when the bug is in NEW state.
> 
> No, After change the bug from New to Post, this button keep existing.

Ahh I misread the code, if it's anything other than assigned it allows you to get to the assigned status in one click.

I still like the convenience though!

> > 2: Only appear to people who have edit permission on the bug.
> 
> Yes
> 
> > 3: When clicked set the user as assigned and the status to ASSIGNED.
> 
> Indeed, It will set the user to assigned, but will not set the status to
> ASSIGNED in the case that this bug's already get changed in the before.

That's a bug! We can do that as this bug or you could open another one please :)

> > 
> > Did I mention, it is awesome?

Not sure I did, it's awesome!!!

Comment 4 Jeff Fearn 🐞 2016-05-12 07:00:03 UTC

I believe this bug can be rejected now that 1335376 has been opened!

Comment 5 Muhammad Tahir 2016-05-12 23:55:08 UTC


*** This bug has been marked as a duplicate of bug 1335376 ***