Sometimes, Bugzilla says 'Bug Processed', but it might not be, yet...

RESOLVED WORKSFORME

Status

()

--
minor
RESOLVED WORKSFORME
17 years ago
6 years ago

People

(Reporter: bugzilla, Assigned: jacob)

Tracking

Details

(Reporter)

Description

17 years ago
If you change a Product, then you get the page saying...

------

Bug processed
 
Changing product means changing version, target milestone and component.
You have chosen a new product, and now the version, target milestone and/or
component fields are not correct. (Or, possibly, the bug did not have a valid
target milestone, component or version field in the first place.) Anyway, please
set the version, target milestone and component now.

------

The first line should probably not say 'Bug processed', should it, as the
process is not complete yet, is it?
Priority: -- → P2
Target Milestone: --- → Bugzilla 2.16
(Assignee)

Comment 1

17 years ago
-> New Bugzilla Product
Assignee: justdave → myk
Component: Bugzilla → Creating/Changing Bugs
Product: Webtools → Bugzilla
Version: Bugzilla 2.12 → 2.12
(Assignee)

Comment 2

17 years ago
Bug 97197 has a patch on it (attachment 47965 [details] [diff] [review]) that fixes this, too.
(Assignee)

Comment 3

17 years ago
-> Me
Assignee: myk → jake
We are currently trying to wrap up Bugzilla 2.16.  We are now close enough to
release time that anything that wasn't already ranked at P1 isn't going to make
the cut.  Thus this is being retargetted at 2.18.  If you strongly disagree with
this retargetting, please comment, however, be aware that we only have about 2
weeks left to review and test anything at this point, and we intend to devote
this time to the remaining bugs that were designated as release blockers.
Target Milestone: Bugzilla 2.16 → Bugzilla 2.18

Comment 5

16 years ago
There's also another case of the page saying Bug Processed before it really is:
When you get a mid-air. Should I file that as a separate bug?
(Reporter)

Updated

16 years ago
Summary: Changing product says 'Bug Processed', but it might not be, yet → Sometimes, Bugzilla says 'Bug Processed', but it might not be, yet...
I think that now that we're templatised, fixing this should be easy (since we
don't produce any output until we know what it is we're producing)
Alas, that's not true for process_bug.cgi, which still produces iterative output.

Comment 8

15 years ago
Works for me on tip, fixed by the various templatization efforts no doubt. 
Breaking dependency, as this is fixed and the dep may not be.
Status: NEW → RESOLVED
Last Resolved: 15 years ago
No longer depends on: 97197
OS: SunOS → All
Priority: P2 → --
Hardware: Sun → All
Resolution: --- → WORKSFORME
Target Milestone: Bugzilla 2.18 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.