Bugs that are associated with a test case can't be reoepend from a resolved states

Assigned to


8 years ago
5 years ago


(Reporter: Kevin R. Ballard, Assigned: Greg Hendricks)




(1 attachment)



8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6 (.NET CLR 3.5.30729)

If a bugzilla issue is associated with a test case, the issue cannot be reopened from a resolved state.

Reproducible: Always

Steps to Reproduce:
1. Create a test case
2. Create a bug
3. Associate the bug to the test case
4. Resolve the bug
5. Attempt to reopen the bug
Actual Results:  
The issue does not reopen, and get a message "The tag "" does not exist"

Expected Results:  
The issue should reopen without error.

Bugzilla 3.4.5

Testopia 2.3.1

Comment 1

8 years ago
So far I am unable to reproduce this. The error message you are receiving makes me suspect something is wrong with the test case. Do you have tags on the test case? The only thing that can throw this error is trying to remove a tag. I assume you are reopening the bug in Bugzilla and not by failing the test case?

Comment 2

8 years ago
I can no longer reproduce this on our installation (I did not make note of which of our test cases/bugs this was occurring on). We were, indeed, trying to reopen the bug from bugzilla, and not be failing the test case. For now, this does not appear to be a valid issue.

Comment 3

5 years ago
Created attachment 832055 [details] [diff] [review]

We ran into the issue bug in a customer installation.

The function bug_end_of_update in ./extensions/Testopia/Extension.pm is calling remove_tag('BUGFIXED') when a bug is reopened.  In the case that this tag does not exist, the error is thrown.

The attached patch calls check_tag('BUGFIXED') before attempting to remove it.  It also fixes the error messages in the remove_tag() functions to include the tag name received.

Please review the patch and let us know if any changes should be made.
You need to log in before you can comment on or make changes to this bug.