Bug 765633

Summary:	Bugzilla queue and feature requests
Product:	[Community] PressGang CCMS	Reporter:	Misty Stanley-Jones <misty>
Component:	Web-UI	Assignee:	Matthew Casperson <mcaspers>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	1.x	CC:	cbredesen, jwulf, lcarlon, lnewson, topic-tool-list
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-02 00:42:12 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Misty Stanley-Jones 2011-12-09 00:09:11 UTC

Matt,

We should probably be using the JBoss Enterprise Application Platform 6 > Documentation queue. I have emailed helpdesk@ to find out who the owner of it is. I assume we can move topic bugs en masse and then we can update the link to the docs.

Also, I've been having a think about topic bugs. I think we should have a table in Skynet where people can enter their Bugzilla ID, and that can be captured in the metadata of the topic. That would allow us to assign bugs to the right person, automatically. Maybe the Bugzilla ID could be part of a "user profile" section, which would have:
* Full Name
* Kerberos ID
* Email address
* Bugzilla ID
* JIRA ID
* Projects they are a writer for
* "Owned" common name and technology tags

Then it would be nice if the "user dashboard" you are working on could use the Bugzilla and JIRA APIs to display a queue of the user's bugs in both systems. In this way, Skynet would become the central place where the work would all be initiated.

What do you think?

Comment 1 Matthew Casperson 2011-12-16 04:20:29 UTC

I've added the ability to attach arbitrary data to a tag and topic, which can include the list of information above. Once I get the required information from the authors I'll populate the database and then being by prepopulating the Bugzilla link with more detailed information (like who the bug is assigned to).

Comment 2 Matthew Casperson 2011-12-19 22:08:44 UTC

The assigned to field is now populated with the Bugzilla Property Tag. The build id field now includes the topic id, envers revision and revision date. See https://bugzilla.redhat.com/show_bug.cgi?id=768806 for an example of the new format.

Bugs assigned through the link on the rendered topic can be searched using the new "Find Bugs" link in the topic id context menu (note this only works for new bugs, not existing bugs).

Comment 3 Matthew Casperson 2012-01-17 00:05:17 UTC

This feature will be implemented when the new server is online. An email will be sent when the change over is to take place.

Comment 4 Joshua Wulf 2012-02-06 09:13:44 UTC

Assignment to a person should probably be dealt with in Bugzilla using subcomponents and owners. 

Otherwise you'll move someone off EAP6 (or they'll leave), and bugs will continue to be assigned to them for the next ten years.

If you have the bug filed against a subcomponent, then you can (re)assign that subcomponent to someone - that way you get the component to person mapping, but its reconfigurable.