| Summary: | I can't set Request For Update flag for UPDATE REQUEST | ||
|---|---|---|---|
| Product: | [ROSA Infrastructure] Websites | Reporter: | Ural Mullabaev <u.mullabaev> |
| Component: | Bugzilla | Assignee: | Pavel Shved <pavel.shved> |
| Status: | RESOLVED FIXED | QA Contact: | ROSA Linux Bugs <bugs> |
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Platform: | --- | ROSA Vulnerability identifier: | |
| RPM Package: | ISO-related: | ||
| Bad POT generating: | Upstream: | ||
|
Description
Ural Mullabaev
2012-07-24 09:58:39 MSK
From the bug history I see that you have set the status to RESOLVED after you made a comment with advisory and buildlist. The workflow, however, requires you to do all the things (prepare advisory, mark as resolved, and request an update) simultaneously, with only one press to "Save Changes" button. Allowing to request an update that relies on a comment that's been already made would cause errorneous requests when your first submission was not correct. That's why you should do it all at once. I suppose that this workflow was not made clear enough in the instruction at http://wiki.rosalab.ru/en/index.php/Requesting_an_Update#What_should_a_maintainer_do . I fixed the instruction (see point 6) to prevent this misunderstanding in the future. I also have requested the update on your behalf. |