Bug 9816

Summary:	add a RESOLVED/REPORTED UPSTREAM
Product:	[Infrastructure] Bugzilla	Reporter:	Alexander Kanavin <alex.kanavin>
Component:	bugzilla	Assignee:	Michael Halstead <mhalstead>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	infras.bug.watcher, Infras.watcher, ross.burton
Version:	unspecified
Target Milestone:	Future
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	No (bug/feature does not impact docs)

Description Alexander Kanavin 2016-06-23 13:13:47 UTC

When we cannot fix a bug in an upstream project, and the most we can do is to report it upstream, it would be good to have a corresponding Bugzilla resolution. None of existing resolutions are a good fit.

Comment 1 Ross Burton 2016-06-23 15:04:04 UTC

Next week Michael, I'll have a chat with you about this. :)

Comment 2 Michael Halstead 2016-06-29 18:28:20 UTC

We currently have WaitForUpstream for open bugs.
It sounds like we need a Resolved -> ReportedUpstream status. Will that do everything we need?

Comment 3 Alexander Kanavin 2016-06-30 13:37:01 UTC

LGTM, but I'd like Ross to comment as well.

Comment 4 Ross Burton 2016-06-30 13:41:51 UTC

Yes, a RESOLVED-ReportedUpstream status would be good.

I think we should then review all current WaitingForUpstream bugs and either move them to NEW (we'll fix this at some point if upstream doesn't) or RESOLVED->Reported Upstream if we're not going to put any more effort into it.

As to the naming of the actual resolution, how about RESOLVED->UPSTREAM?

Comment 5 Alexander Kanavin 2017-09-18 13:53:29 UTC

Ping?

Comment 6 Michael Halstead 2017-09-18 17:46:42 UTC

Thank you for this ping. The new status is in place please let me know if any changes are still required.

Comment 7 Alexander Kanavin 2017-09-19 11:10:18 UTC

Thanks, seems fine now.