If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Cannot assign a different user to a test case in a test run

RESOLVED FIXED

Status

Testopia
Test Runs
--
major
RESOLVED FIXED
11 years ago
10 years ago

People

(Reporter: Costa Galanis, Assigned: Greg Hendricks)

Tracking

Details

(URL)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: 1.2

No matter what value is entered in the text field next to the Assign button when expanding a Test Case in the Test Run page, the value is reset to the default when clicking the button, making it impossible to assign a test case to anyone but yourself.

Reproducible: Always

Steps to Reproduce:
1. Edit an incomplete Test Run
2. Expand a Test Case that has not been completed
3. Try to assign the test case to another user by entering his/her email address in the corresponding field and press the "Assign" button
Actual Results:  
The test case is assigned to me, the user currently logged in

Expected Results:  
The test case gets assigned to the desired user

This seems to be a UI bug, not a problem with the backend of the system. It may be related to the same issue described in bug 376670, which is also causing me some headaches.

Comment 1

10 years ago
I also noticed this issue, the work around is to click on the classic interface; in it the drop down list works and you can assign a different test case owner for that particular run.
(Reporter)

Comment 2

10 years ago
Unfortunately, I seem to be blocked from using that workaround as well. I am encountering an issue with the non-standard drop down widget used in many places (such as the Assignee field you referenced in Comment #1 or the Environment field in the same classic interface page) where clicking the arrow does not fetch anything for me (the list is empty), and if I manually enter anything in these fields, my entry immediately gets deleted when I click anywhere else, such as the Commit button :(.

The symptom is identical to what you yourself reported in Bug 383246, but I'm seeing it everywhere that custom drop down is used, not just for Environments.

Comment 3

10 years ago
I saw this issue when we tried to upgrade to the latest version of DOJO (dropdowns stopped working). I would use the DOJO library delivered within the tar distribution. I am not expert but it might also be something with DOJO library permissions at the OS level.

If you can not select user that owns test case, test case plan and test case run, it is a blocking issue as uit prevents you from distributing and managing the work properly (from the project management perspective)
(Assignee)

Comment 4

10 years ago
(In reply to comment #3)
> I saw this issue when we tried to upgrade to the latest version of DOJO
> (dropdowns stopped working). I would use the DOJO library delivered within the
> tar distribution. I am not expert but it might also be something with DOJO
> library permissions at the OS level.
> 
The latest version of dojo does not work with the current version of Testopia. 
I have upgraded it for Testopia 1.3, but I had to make a lot of changes for it to work.


Comment 5

10 years ago
On a mroe general note, it would be nice if when the bug is resolved, it also contains info on the CVS tag that contains the fix, so that we know what tag to use when building a tar. I have 4 bugs that are fixed, and know clear idea how to get them (no tag information is provided in the notes when bug is fixed; as per my email from earlier today)

(In reply to comment #4)
> (In reply to comment #3)
> > I saw this issue when we tried to upgrade to the latest version of DOJO
> > (dropdowns stopped working). I would use the DOJO library delivered within the
> > tar distribution. I am not expert but it might also be something with DOJO
> > library permissions at the OS level.
> > 
> The latest version of dojo does not work with the current version of Testopia. 
> I have upgraded it for Testopia 1.3, but I had to make a lot of changes for it
> to work.

(Assignee)

Comment 6

10 years ago
    Checking in template/en/default/testopia/caserun/short-form.html.tmpl;
    /cvsroot/mozilla/webtools/testopia/template/en/default/testopia/caserun/short-form.html.tmpl,v  <--  short-form.html.tmpl
    new revision: 1.20.2.2; previous revision: 1.20.2.1
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED

Comment 7

10 years ago
works as expected
You need to log in before you can comment on or make changes to this bug.