View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002022 | HTML & PERL | Bug Report | public | 2013-03-09 23:51 | 2014-05-09 03:58 |
| Reporter | Hinoe | Assigned To | DerIdiot | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0002022: Assigned creqs on areas the owner has no power over treat the owner wrongly | ||||
| Description | With creq handling powers, be it over an entire system (as full/senior mod) or just a smaller area (as creq handler or language verifier), one has options such as ignoring fields and adding/reading mod-only notes. Additionally, all comments one makes change the creq status to HOLD. When one does not have creq handling powers over such an area, but nevertheless becomes its owner by virtue of someone who holds such power assigning the creq to them, the creq misbehaves by not acting the way described above. Aside from being able to see the usernames of everyone involved in the creq and having the power of granting/denying it, the user sees the creq as if they were not the owner, and their comments can change the status to RETURN as well. | ||||
| Steps To Reproduce | 1. Pick a regular account and issue a creq. 2. Open it as a full/senior mod (or creq handler or language verifier if appropriate). 3. Assign it to an account without full/senior mod or creq handler or language verifier status on that area. 4. Check it as the new owner. | ||||
| Additional Information | In my experience, whether the owner is also the issuer or not makes no difference, nor does whether their main role is User or Adv. User. This may (or may not) be related to the issue I reported in the past about being unable to grant a creq that was assigned to me (which as I recall is already fixed). | ||||
| Tags | No tags attached. | ||||
