PM Support Quick Reference TFS Guide

Support Priority:

Bug Writing:

P1 - Emergency! Devs need to drop everything and work on

this Immediately. Patch required as soon as possible.
P2 - Severe bug, likely with workaround. These are the
highest Priority issues developers are working on during
sprints.
P3 - High bug, with relatively easy workaround. These are
issues Developers can likely fix before regression, but are not
priority.
P4 - Medium bug, likely not affecting functionality. These are
Issues developers can focus on fixing after everything else.

When creating TFS please fill out the following: Title, Area, Iteration (backend/bug), and
Support Priority Level. Please simply add a period to the description and steps on the main
tab. Vanguard will fill these out. On the support tab, fill out Business Alias, Account Email,
App/Emp Record URL, Description, and Steps to Reproduce. This will make sure your bug
is seen by Vanguard. Remember, being as accurate as possible increases the probability of
a successful resolution to the issue.
Things like Browser/OS are important and can help get your issue fixed faster.
Dev tools (console and network) will help if they're in the bug from the
beginning, rather than having to go back to get them.
Who does this happen to? Is it everyone, only one location, only one
manager/employee? How often?
Can you reproduce it yourself?
If an error message pops up, a timestamp from your computer will help ensure
we find something in the error logs, rather than guessing if an error is the right
one.
If an API call is being made, the name of the API and RAW data is preferred and
can help resolve the issue faster.
If the issue is everify related, an example case number should always be
provided so we can see the message communication on the backend.

Severity:
Blocking - As critical below, but with data loss. More global,
blocks anything else from being done, no workaround exists.
This needs to be fixed immediately. Never gets moved to
next release.
Critical - Crash or loss of functionality, does not block further
testing. Usually no workaround exists, or workaround is
extremely difficult to deal with. Never gets moved to next
release.
High - Major issue, but no crash or data loss. Workaround
usually exists. Should not be moved to next release.
Medium - Issue, but no crash or data loss. Workaround exists
and is usually pretty easy. May be moved to next release.
Low - Usually cosmetic issues (fit and finish), fix if there is
time, does not affect functionality, can be moved to next
release.

Patch Priority:

If a button doesn't work when clicking it

Collect Browser Info
Open Dev Tools
Click "Network"
Refresh Page
Click button again
Screen Capture/Copy Info

1 - Immediate patch - As soon as the bug is fixed, smoketest

and deploy asap.
2 - Fix for next patch - This should be fixed in the next patch,
unless the bug was filed 2 days before the next patch date,
then it rolls over into the following patch.
3 - Fix before regression - This bug should be fixed in a patch
and deployed before regression.
4 - Fix during regression - This bug should be fixed in the next
release, but does not require a patch. It can be fixed in
regression.
5 - On Hold - This bug is not priority to be fixed. It has been
put on the backlog by product owners, or determined we
have more important fixes at the time.

Repeat for "Console" in Dev Tools

If an image/webpage doesn't display correctly

Collect Browser Info
Open Dev Tools
Click "Console"
Refresh Page
Screen Capture/Copy Info
Did we clear cache?
Did we clear cookies if something related to login/permissions?
Does something look weird on the applicant/employee record notes?
Are there multiple notes with the same timestamp (duplicate onboarding)
Did they separate, rehire, transfer, transfer, separate, hire, rehire, transfer

(overlapping dates cause things to become confused)

Bug Statuses:

Who to email:
Vanguard - Any time you have a question. However, if the
question is a bug, or will need investigation, please log a tfs
along with the email.
Please keep vanguard cc'ed on any replies if they are on
a thread.
The Vanguard list includes Andrea, Josh, Jen, Mark, and
Brad
Devops - Any time there is a server issue, or reporting seems
down. Please also email Vanguard, or just email Vanguard so
the team can work with dev ops.
Devopsdesk - Only if Vanguard cannot be reached and there
is a server issue.
Any Individual - Never, your bug will get faster attention if
you email the groups.

Patch Queries:

Troubleshooting:

Closed - Issue has been resolved as will not address or duplicate, or has been tested in
regression and will be fixed in the release. There will be a reason on the bug to indicate
how it was closed.
Closed in QA-Prod - Issue has been fixed for a patch and will be deployed in the next patch.
On Hold - Issue cannot be reproduced and will not be looked at until additional reports of
the bug come through or the issue is surfaced as extremely critical. This state also may be
seen if logging has been added to try to get better info on a bug that cannot reproduced.
You need to ask if you want an update on this status as nobody will be actively working
on it.
Ready for Testing - If you get a bug assigned to you with this status, it is an error. This is a
bug that should have been assigned to QA. Please let Josh know if you have a bug assigned
to you with this status.

(these are all shortcuts on your TFS home page)

1. Fixed in Dev - Issue has been fixed in initial test environment and is eligible for patch if fix is approved.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+1.
+Fixed+in+Dev+awaiting+validation&_a=query

Training Page 1

Patch Queries:

(these are all shortcuts on your TFS home page)

1. Fixed in Dev - Issue has been fixed in initial test environment and is eligible for patch if fix is approved.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+1.
+Fixed+in+Dev+awaiting+validation&_a=query
2. Merge Candidate - Fix has been approved in initial test environment and bug is eligible for patch.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+2.+Merge+Candidate&_a=query
3. Merge to Production - Bug has been tested in initial test environment and is being put into the patch process.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+3.+Merge+to+Production&_a=query
4. Ready to be built - Bug has been merged to the secondary test environment and will likely be in the next patch as long as testing is approved.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+4.+Ready+to+be+built&_a=query
5. Patch is being validated - Bug is being tested in secondary test environment.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+5.
+Patch+is+being+validated&_a=query
6. Ready to deploy - Bug has been tested in secondary test environment and has been approved. This bug will definitely be in the next patch.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+6.+Ready+to+deploy&_a=query
7. Fixed and deployed as patch - This is a list of bugs that have already been deployed to live production servers.
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/_workItems#path=Shared+Queries%2FDevelopment%2FProduction%2FPatches%2FBugs+ -+7.
+Fixed+and+Deployed+as+patch&_a=query

Support Queries:

(these are all shortcuts on your TFS home page)

1. All open support bugs sorted by support priority:

http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/Support%20and%20Implementation/_workItems#path=Shared+Queries%2FSupport+and+Implemen tation%
2FAllSupportBugsBySupportPriority&_a=query
2. Bugs that need support attention (In a perfect world, wed want to keep this under 5 bugs, but anything under 10 is manageable):
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/Support%20and%20Implementation/_workItems#path=Shared+Queries%2FSupport+and+Implemen tation%
2FSupportDashboard%2FNeedsSupportAttention&_a=query
3. Bugs that need YOUR attention:
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/Support%20and%20Implementation/_workItems#path=Shared+Queries%2FSupport+and+Implemen tation%
2FSupportDashboard%2FNeedsMyAttention&_a=query
4. Important (non blocking) support bugs (note, this should never be more than about 5 bugs. If there are more than 5 bugs, we will not be able to identify what is
important inside of this query and it will be useless). To get a bug into this query, support priority must be 1 or 2, severity must be blocking or critical, and you must
put top priority in the history:
http://pm-vtfs-ap2012:8080/tfs/PrimaryCollection/PM2012/Support%20and%20Implementation/_workItems#path=Shared+Queries%2FSupport+and+Implemen tation%
2FSupportDashboard%2FImportant+Support+Issues&_a=query

Training Page 2