|
|
| (15 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | = ATS Frequently Asked Questions =
| |
| | | | |
| − | == Workflows ==
| |
| − |
| |
| − | === What is the basic workflow of an Action in ATS ===
| |
| − |
| |
| − | (End User) Generate Action for Enhancement/Issue<br>
| |
| − | - Select bug icon in top right corner of OTE window corresponding to Action OR select "A" icon in top right window of ATS Navigator or ATS World.<br>
| |
| − | - If bug icon: Enter title for Action and press Ok<br>
| |
| − | - If "A" icon: Select OSEE Product, Select LBA Configuration, Select version problem was found against and Select OTE_SW, OTE_HW or both depending on whether the Action is against the Software or Hardware portions of OTE.<br><br>
| |
| − |
| |
| − | (End User) Identify State<br>
| |
| − | - Edit Action to include required/optional fields and select "Complete"<br><br>
| |
| − |
| |
| − | (Endorser [configured]) - Endorse State<br>
| |
| − | - Validate information provided in Identify State<br>
| |
| − | - Edit Action and to provide more information<br>
| |
| − | - Select impacted Product/Aspects<br><br>
| |
| − |
| |
| − | (Product Leads/Dev Engineers) - Analyze State<br>
| |
| − | For each product impacted<br>
| |
| − | - Analyze Action and Assign Aspects impacted<br>
| |
| − | - Record estimated hours to complete<br><br>
| |
| − |
| |
| − | (Management/Product Leads) - Authorize State<br>
| |
| − | - Approve Action for implementation<br><br>
| |
| − |
| |
| − | (Product Leads/Dev Engineers) - Implementation State<br>
| |
| − | For each product impacted<br>
| |
| − | - Assign engineers to implement changes to Aspects impacted<br>
| |
| − | - Continually record percent complete and hours spent until completion<br><br>
| |
| − |
| |
| − | (End User) - Validation State<br>
| |
| − | - Validate that the resolution meets the users needs<br><br>
| |
| − |
| |
| − | Completed State<br>
| |
| − | - Changes committed to repository and ready for release
| |
| − |
| |
| − | == Tasks ==
| |
| − |
| |
| − | === What is a Task? ===
| |
| − |
| |
| − | === How do I create tasks for a Team Workflow ===
| |
| − | There are a few ways to easily create tasks for a Team Workflow.
| |
| − | <ol>
| |
| − | <li>From the "Task" tab off the Team Workflow Editor, select the "New Task"</li>
| |
| − | <li>Right click on "Task" tab table off the Team Workflow Editor, select "New Task"</li>
| |
| − | <li>Import tasks from Simple List</li>
| |
| − | <ol>
| |
| − | <li>Select pulldown from toolbar off the Team Workflow Editor, select "Import Tasks via Simple List"</li>
| |
| − | <li>Enter one task title per line.</li>
| |
| − | <li>Select an assignee for the new Task(s), if desired.</li>
| |
| − | </ol>
| |
| − | <li>Import tasks from Spreadsheet</li>
| |
| − | <ol>
| |
| − | <li>[http://www.eclipse.org/osee/documentation/ats/support/ATS%20Task%20Import.xml Download sample excel spreadsheet]</li>
| |
| − | <li>Edit spreadsheet, providing one row per task to be created</li>
| |
| − | <li>Ensure that Originator and Assignee cells have name of existing user in your OSEE database</li>
| |
| − | <li>Select pulldown from toolbar off the Team Workflow Editor, select "Import Tasks via Spreadsheet".</li>
| |
| − | </ol>
| |
| − | </ol>
| |
| − |
| |
| − | == Configuration ==
| |
| − |
| |
| − | === How do I configure ATS for multi-branch committing ===
| |
| − | ATS can be configured to support committing artifact changes to multiple variant branches. This is done through configuring ATS to use Versions and configuring each version to the branch that it manages. See http://wiki.eclipse.org/OSEE/ATS/Users_Guide.
| |
