RE: Production vs. Development Defects

Todd -

    In my project, if issues are found during QA testing (and hence are not 
"Done"), we add separate tasks to the current story for the developer to fix 
the issue, and for the QA tester to verify that the issue has been fixed. Once 
the code has gone to Production, we use standard V1 defects to track, 
prioritize and work these issues.

Thanks,

David
__________
David Shaffer
IT Manager - Enterprise Risk Management
Corporation Service Company
(800)-927-9801 x3407
www.cscglobal.com<blocked::http://www.cscglobal.com>
Innovating Service and Technology for Over 100 Years

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd Johns
Sent: Friday, March 02, 2012 10:45 AM
To: [EMAIL PROTECTED]
Cc: Robert Turley; Celeste Garcia; Karen Kelley
Subject: RE: Production vs. Development Defects

Not sure I understand what you mean by an internal/external button.  Does it 
add some kind of attribute to the work item to report off of?

________________________________
From: [EMAIL PROTECTED] [EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] [EMAIL 
PROTECTED]
Sent: Friday, March 02, 2012 8:52 AM
To: [EMAIL PROTECTED]
Cc: Robert Turley; Celeste Garcia; Karen Kelley
Subject: RE: Production vs. Development Defects
The easy answer is use an internal/external button (you can create one of these 
as a custom entry).  We have found that can be misused, so we categorize 
external defects as those specifically associated to a service call in our CRM 
system.  That way we can track exactly where it came from and there is no 
argument about if it is REALLY external or not.

Hope This Helps,
jim

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Todd Johns
Sent: Friday, March 02, 2012 9:42 AM
To: [EMAIL PROTECTED]
Cc: Robert Turley; Celeste Garcia; Karen Kelley
Subject: Production vs. Development Defects

We are using the Defect work item type for both issues found in released code 
and also issues found in test as we develop new code.  We want to start 
distinquishing which defects were found in production and which defects were a 
result of the QA/Testing process for new code.

Anyone have a best practice for this?
--
You received this message because you are subscribed to the Google Groups 
"VersionOne-users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/versionone-users?hl=en.
--
You received this message because you are subscribed to the Google Groups 
"VersionOne-users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/versionone-users?hl=en.
--
You received this message because you are subscribed to the Google Groups 
"VersionOne-users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/versionone-users?hl=en.

-- 
You received this message because you are subscribed to the Google Groups 
"VersionOne-users" group.
To post to this group, send email to [EMAIL PROTECTED]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/versionone-users?hl=en.