Bug 856799 - [rfe] Ability to delegate tester/multiple tester(s) after creating a test run
[rfe] Ability to delegate tester/multiple tester(s) after creating a test run
Status: NEW
Product: TCMS
Classification: Other
Component: Web UI (Show other bugs)
Devel
Unspecified Unspecified
unspecified Severity unspecified
: ---
: 4.0
Assigned To: Yang Ren
tools-bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2012-09-12 16:00 EDT by Corey Welton
Modified: 2016-06-23 00:36 EDT (History)
7 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Nitrate 3.8.0
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Corey Welton 2012-09-12 16:00:24 EDT
Description of problem:

We have a product with well over 200 testcases that need to be executed amongst multiple members on a team. 

When creating a test run, the run manager/creator has the ability to initially assign a default tester for all cases or leave that field blank.  However, after creation, there is no way to subsequently modify the Tester (or Assignee) fields to adequately delegate assignment execution.  

In short, you're left with a slew of testcases in a run that cannot in any easily measurable way be assigned out to multiple members on a team.

I'm not sure it's valid to assume that...

a) one user will execute all testcases in a run, or 
b) all cases are by default unassigned, leaving them basically in a "free-for-all" mode

...covers all valid use cases for creating test run.

Secondly, I'm not sure why these can't be changed after the fact, i.e., after creating a test run.
Comment 1 Corey Welton 2012-09-12 16:04:40 EDT
Edit: It does look like I can change Assignee using the Cases dropdown, but I'm not sure that's 100% adequate. A similar dropdown for "Tester" would be better.

Note You need to log in before you can comment on or make changes to this bug.