Closed Bug 565523 Opened 16 years ago Closed 16 years ago

Add EXPIRED to addons.mozilla.org product

Categories

(bugzilla.mozilla.org :: Administration, task)

Product:
bugzilla.mozilla.org
Component:
Administration
Platform:
All
Other
Type:
task
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: clouserw, Assigned: marcia)

Details

We'd like to have the EXPIRED resolved status available for AMO bugs. thanks.
Not an IT issue.
Assignee: server-ops → marcia
Component: Server Operations → Bugzilla: Keywords & Components
QA Contact: mrz → timeless
Sorry, resolutions are Bugzilla-wide, so your request isn't possible at all. EXPIRED was something that was used a long time ago and is restricted to use by gerv alone. It's not a valid resolution today and should not be considered as such. May I recommend INVALID, WORKSFORME, or INCOMPLETE for your use case instead?
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
A bug that was valid but is no longer valid, as is the case with many AMO bugs, fits EXPIRED better than any of your recommendations. I think we should add it globally if we can't add it per product.
Why not just use INVALID? Or WORKSFORME if you're worried that INVALID will hurt someone's feelings.
We are using INVALID, it's just not as accurate as EXPIRED.
clouserw: the problem is that there's code in Bugzilla which restricts this resolution to me only, and changing that is a pain. Is there a search I could run that returns the bugs you want to resolve in this way? I'd be happy to resolve them for you. Gerv
Thanks for the offer. As we rewrite AMO in python, while triaging bugs we come across a lot that are no longer relevant and I wanted to classify them more appropriately. Since it will be an ongoing thing as we sort through bugs let's not worry about it. I guess this bug should have been "Don't hardcode EXPIRED to Gerv" :)
Reopening for clarification of comment 8
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
(In reply to comment #8) > says that james@mozilla.com is using EXPIRED for the support product. How is > that possible? That was a bug... I fixed a while ago in bug 552158.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → WONTFIX
(In reply to comment #10) > That was a bug... I fixed a while ago in bug 552158. fixed it*
So this isn't hardcoded to Gerv, and it was apparently available for a product in the past. I'm confused what the problem with turning this on for AMO is.
Sounds like a pretty reasonable request.
Status: RESOLVED → REOPENED
Resolution: WONTFIX → ---
(In reply to comment #12) > So this isn't hardcoded to Gerv, and it was apparently available for a product > in the past. I'm confused what the problem with turning this on for AMO is. Yes, it is hardcoded to Gerv. Some of the code that restricted it to only him was lost in the Bugzilla 3.2->3.4 upgrade, but the bug that incorrectly permitted that to occur has since been fixed (bug 552158). It is NOT possible to restrict the EXPIRED resolution to the AMO product without some massive hacking of bmo's code, which I'm unwilling to do because it's very likely to cause problems that I can't even begin to hypothesize. Resolutions are not designed to be per-product, and there's just too many things that could possibly break by such a change. If we ever do decide to open EXPIRED up, it'll be bmo-wide for everybody to use. Just for your information, last Friday (5/14), Gerv started a discussion thread among the bmo admins about doing just that. However, as it currently stands, the EXPIRED resolution is only available for use by Gerv in special circumstances. If a change in policy results from that e-mail thread, I will reopen this bug. I hope this answers your questions. Let me know if you have any other comments.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → WONTFIX
(In reply to comment #14) > If we ever do decide to open EXPIRED up, it'll be bmo-wide for everybody to > use. Just for your information, last Friday (5/14), Gerv started a discussion > thread among the bmo admins about doing just that. However, as it currently > stands, the EXPIRED resolution is only available for use by Gerv in special > circumstances. If a change in policy results from that e-mail thread, I will > reopen this bug. > > I hope this answers your questions. Let me know if you have any other comments. Awesome, how can other people watch/participate in this discussion?
(In reply to comment #15) > Awesome, how can other people watch/participate in this discussion? It's a private mailing list for bmo administration issues, so you can't watch it directly. Gerv included a link to this bug in his original mail about opening EXPIRED up, but if you have something specific you would like added to the discussion, I'll be happy to relay your comment.
Shaver has said he'd prefer us to reduce the number of resolution options rather than increase it, e.g. by merging EXPIRED, INVALID and WONTFIX into some sort of INACTIVE resolution (or a better name). He thinks that closing comments with rationale are better than single-word summaries. Given that, I suggest that the opening up of EXPIRED is unlikely, and you may want to take the approach he suggests. But, as I said, I'm happy to EXPIRE lists of bugs if you send me a URL. (Note that you can have a buglist of individual bugs: https://bugzilla.mozilla.org/buglist.cgi?bug_id=500000,500001 Gerv
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.