Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be available on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 818215 - We need the ability to edit the ownership of test cases.
Summary: We need the ability to edit the ownership of test cases.
Keywords:
Status: ASSIGNED
Alias: None
Product: TCMS
Classification: Other
Component: Web UI
Version: 3.6
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 4.0
Assignee: Yang Ren
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-02 13:39 UTC by Jon Allen
Modified: 2021-02-16 02:43 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Jon Allen 2012-05-02 13:39:15 UTC
Description of problem:
When a testcase owner moves to a different role or leaves the company, we need to assign ownership to another team member. It seems that currently there is no way to accomplish this using the UI.

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

How reproducible:
Very

Steps to Reproduce:
1. Go to Planning -> Search Plans.
2. Type "blittle" into the Owner field and click Search.
3. In the search results, select "RHSM Web"
4. Note that none of the resulting testcases can be edited because they are owned by blittle.
  
Actual results:
There is no way to edit the testcases.

Expected results:
We need a way to edit the testcases.

Additional info:

Comment 1 yawei Li 2012-05-16 08:05:23 UTC
currently normal user has no permission to change author, and can't edit cases owned by others.
You can send mail to tcms-admin-list for changing the author.

In TCMS 4.0, we plan to provide each team's leader can change these info batch.

Comment 2 yawei Li 2012-05-28 06:13:46 UTC
in TCMS 4.0, consider admin changing the authors in batch.


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