Bug 1394620 - [RFE] Add the ability to set a default status for a component
Summary: [RFE] Add the ability to set a default status for a component
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Bugzilla
Classification: Community
Component: Bugzilla General
Version: 4.4
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified vote
Target Milestone: ---
Assignee: PnT DevOps Devs
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-14 04:38 UTC by Lucy Bopf
Modified: 2016-11-21 01:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-21 01:47:47 UTC


Attachments (Terms of Use)

Description Lucy Bopf 2016-11-14 04:38:58 UTC
Raised in response to https://engineering.redhat.com/rt/Ticket/Display.html?id=426761.

I am requesting an enhancement that enables a user (or the Bugzilla team) to set  a default status for a particular component. This would mean a bug's status is automatically set to whatever the component owner prefers when that bug moves to that component.

An example use case:

I'd like to be able to set the default status to 'NEW' when a bug is moved from another component to the 'Red Hat OpenStack Platform' product + the 'documentation' component. We see bugs commonly moved from engineering components to the documentation component, but the status remains on whatever that team had set it to, and bugs appear to be in motion when they are not. Ideally, the status would be reset when it's given to a new team.

Comment 1 Jeff Fearn 🐞 2016-11-14 05:23:18 UTC
This would be a pretty invasive change for minimal business benefit.

If your component has a non-Human default owner your PM could set-up a Rules Engine rule to set the status to NEW if that user owns a bug.

Comment 2 Jeff Fearn 🐞 2016-11-21 01:47:47 UTC
I think the Rules Engine is a better place for this logic than a code change. Please consult with your Project Management rep to get a rule added.


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