Bug 2512 – RFE: per-state timers to expedite bug resolution

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 2512 - RFE: per-state timers to expedite bug resolution

Summary:	RFE: per-state timers to expedite bug resolution

Status:	CLOSED WONTFIX

Aliases:	None

Product:	Bugzilla
Classification:	Community
Component:	Bugzilla General (Show other bugs)
Sub Component:
Version:	2.18
Hardware:	All Linux

Priority	medium Severity medium (vote)
Target Milestone:	---
Target Release:	---
Assigned To:	David Lawrence
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	1999-05-03 14:23 EDT by Jeff Johnson
Modified:	2008-05-01 11:37 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2005-08-23 15:28:25 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jeff Johnson 1999-05-03 14:23:34 EDT

I'd like to see fixer-person settable per-bug timers with
per-state transition default values.

I'd use them to automate certain policy decisions within
bugzilla such as

1) Any NEW bug will be ASSIGN'ed to package owner within
N (e.g. N=1) days.

2) Every ASSIGN'ed bug will have a developer chosen
estimated time until fix appears. The estimated time shall
be chosen within M (e.g. M=7) days or the bug will
automatically be sent to the "Bozo-of-the-Week" for
expedited choosing.

3) Every bug in VERIFY'ed category will be automatically
expedited after X (e.g. X=7) days.

Comment 1 David Lawrence 2005-08-23 15:28:25 EDT

No longer relevant due to new release of Bugzilla. Please reopen as new bug if
these requests are still needed.

Note You need to log in before you can comment on or make changes to this bug.