This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 240311 - [80cat] Add feature to allow users or tribe leaders to delete assignments
Summary: [80cat] Add feature to allow users or tribe leaders to delete assignments
Status: VERIFIED FIXED
Alias: None
Product: qa
Classification: Unclassified
Component: Synergy (show other bugs)
Version: 8.0
Hardware: All All
: P3 normal with 3 votes (vote)
Assignee: Vladimir Riha
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-12 02:58 UTC by Lou Dasaro
Modified: 2015-10-31 19:01 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lou Dasaro 2014-01-12 02:58:38 UTC
This is to request the following feature in Synergy:

As a tribe leader,
I would like to be able to undo an assignment for a member of my tribe.
So that I can more efficiently manage testing performed by my tribe.
(In case I made an error in making the assignment and for similar reasons)


As a participant tester,
I would like to be able to remove an assignment for which I previously volunteered.
So that I can more efficiently manage my own testing.
(In case I made an error in volunteering for the assignment)
Comment 1 Vladimir Riha 2014-01-22 19:45:53 UTC
The think is, if someone is required by leader/manager to execute test assignment, this would practically allow him/her to delete the assignment without any testing. I'm just not sure if this is a good idea.

So there are 3 possibilities:
 #1 allow user to delete his/her assignment 
 #2 allow tribe leader to delete ANY assignment for his/her tribe members
 #3 save to each assignment flag "created by" thus user can remove assignment only if user === created by, tribe leader can only remove assignment if tribe leader === created by (and of course manager beats them all)

#1 and #2 are easy, but I like #3 as it combines best from all. 

Jirko, what do you think about this? Should it be possible?
Comment 2 Vladimir Riha 2014-01-22 20:02:27 UTC
(In reply to Vladimir Riha from comment #1)
>  #3 save to each assignment flag "created by" thus user can remove
> assignment only if user === created by, tribe leader can only remove
> assignment if tribe leader === created by (and of course manager beats them
> all)
> 

More accurately it would be

a) For volunteers:  

user trying to delete === assignee && created by user

b)  For tribe assignment

user trying to delete === tribe leader && created by tribe leader && assignee is member of leader's tribe
   - possibly also check if specification is in leader's tribe but not sure if this would be critical
Comment 3 Jiri Kovalsky 2014-01-22 20:28:56 UTC
I agree with proposed solution #3 of course. If I volunteer and create my own assignment, I should be allowed to delete it later if I find out I am badly busy. If I am tribe leader I can delete all assignments created for any member of my tribe AND test specification in my tribe's responsibility. I think tribe leaders could also delete volunteer assignments within their tribes if they communicate it with the person in advance. Manager can do whatever s/he wants.
Comment 4 Lou Dasaro 2014-01-23 03:45:04 UTC
Agree, #3. But "tribe leaders could also delete volunteer assignments within their tribes" is via system, while "if they communicate it with the person in advance." is procedural (non-system).
Comment 5 Jiri Kovalsky 2014-01-23 05:17:07 UTC
Yes, I understand your concern Lou but I would consider it both confusing and impolite if somebody else (even being that my tribe leader) deleted my assignment I had created voluntarily. Synergy could ask for a short justification in such case and then send at least an automated message to me and tribe leader about such action to avoid procedural complications.
Comment 6 Lou Dasaro 2014-01-23 07:06:00 UTC
+1 Sounds good!
Comment 7 Vladimir Riha 2014-01-23 15:24:19 UTC
Should be almost done now.  If tribe leader removes member's assignment, it sends email notification (if Synergy is set to && user has enabled notifications).

What's left is the asking for justification part (currently it sends only email about the assignment).
Comment 8 Vladimir Riha 2014-01-23 17:07:56 UTC
fixed in #617
Comment 9 Lou Dasaro 2014-01-28 07:04:56 UTC
I can delete an assignment I volunteered for, but I can't seem to delete an assignment (where the assignee was mr_lou_d).
Comment 10 Vladimir Riha 2014-01-28 08:23:57 UTC
I'm sorry for that, I believe I've fixed it. Could you please give it another try (changes will be live in ~10 minutes, after 8:30 UTC) ?
Comment 11 Lou Dasaro 2014-01-29 03:38:52 UTC
Thanks, both use cases now work. However, I did NOT receive any email notifications. I don't know how to enable notifications in Synergy as a user (shouldn't this be ON by default?). I also don't know whether Synergy itself is set to enable notifications.
Please advise.
Comment 12 Vladimir Riha 2014-01-29 07:36:47 UTC
Yes, Synergy as such does not send email notifications related to assignments right now, it is turned off on purpose but I believe it could be turned back on for NetCAT assignments. 
Jirko, do you want me to enable it or will you do it later?

Each user can then disable notifications related to test assignments in his profile page ([1], by default it is on)


[1] http://services.netbeans.org/synergy/client/app/#/user
Comment 13 Jiri Kovalsky 2014-01-29 09:21:48 UTC
Yes, I just turned it on, because I am going to create NetCAT assignments today.