Bug 1374109

Summary: Add UNCONFIRMED state to Bug Status Workflow
Product: [Community] Bugzilla Reporter: Matt Tyson 🤬 <mtyson>
Component: Bugzilla GeneralAssignee: PnT DevOps Devs <hss-ied-bugs>
Status: CLOSED WONTFIX QA Contact: tools-bugs <tools-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4CC: huiwang, mtahir, qgong
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-01-24 00:00:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Matt Tyson 🤬 2016-09-08 01:05:24 UTC
In the 4.4 to 5.0 merge the UNCONFIRMED bug state and code references have crept back in.

Since we don't actually use this state, we should remove the references to it in the code and admin pages.

Comment 1 Jeff Fearn 🐞 2016-09-14 06:10:12 UTC
This has minimal impact and AFAICT there is no compelling reason to prevent community products from using it.

Comment 2 Matt Tyson 🤬 2016-09-14 06:25:41 UTC
(In reply to Jeff Fearn from comment #1)
> This has minimal impact and AFAICT there is no compelling reason to prevent
> community products from using it.

Due to our other customizations in bugzilla, it doesn't actually work at all.

Comment 3 Jeff Fearn 🐞 2016-09-14 22:19:58 UTC
(In reply to Matt Tyson from comment #2)
> (In reply to Jeff Fearn from comment #1)
> > This has minimal impact and AFAICT there is no compelling reason to prevent
> > community products from using it.
> 
> Due to our other customizations in bugzilla, it doesn't actually work at all.

Can you provide more information on what teh customizations are and how they break it?

Comment 4 Matt Tyson 🤬 2016-09-14 23:00:22 UTC
The SchemaChange extension enforces valid bug states and transitions between those states.

UNCONFIRMED is not a valid state in the CDW, so the extension removes it.

Comment 5 Jeff Fearn 🐞 2016-10-14 00:50:53 UTC
I think we can add UNCONFIRMED back in easily enough and just disable it by default so it isn't offered on CDW products.

Comment 6 Jeff Fearn 🐞 2016-11-07 06:23:31 UTC
Add it back in to the right place, it won't be visible on products not using it.

Comment 7 Jeff Fearn 🐞 2019-01-24 00:00:58 UTC
In preparation for entering maintenance mode we are closing bugs that are unlikely to be scheduled in maintenance sprints.