1 / 1

MCESA TFS ticket nomenclature for bug submissions

Understand the ticket naming convention for bug submission in training environment using TFS. Learn how to classify and submit TFS tickets as agreed upon by the team. Follow examples for effective bug/issue reporting.

sari
Download Presentation

MCESA TFS ticket nomenclature for bug submissions

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MCESA TFS ticket nomenclature for bug submissions David is working in the training environment on the ODCT R1V1 application. He is running through an Observation Cycle and encounters a bug/issue that is now preventing him from moving forward in the application. David submits a TFS ticket in the MCESA REIL/Release 1/Sprint “X” The classification of the ticket naming convention should follow the examples listed below as the team agreed upon David’s TFS ticket would look like this in the “Title” line of the ticket: ODCT R1V1.PM.TRN: <bug/issue description> ODCT.R1V1.PM.TRN: <bug/issue description>

More Related