| General | Editorial | Need clearer explanation of process steps for both data custodian and tester | Kay Clinard | 5/13/2014 | | Open |
| General | Editorial | Need instructions on how application and PICs files are handled | Kay Clinard | 5/13/2014 | | Open |
| General | Editorial | 1) Data custodian sends files to CB 2) CB reviews and sends files To TL 3) TL reviews, and contacts Data custodian to schedule test 4) Test scheduled 5) Test conducted 6) Test results sent to CB 7) CB reviews and sends to Data Custodian and posts to | Kay Clinard | 5/13/2014 | | Open |
| General | Editorial | HW Configuraiton - Do we need the particular client side HW platform characteristic? Browser number etc. | John Teeter | 5/15/2014 | | Open |
| General | Editorial | the user account credentials problem is a blocker. It changes the dynamics of the entire test procedure. | John Teeter | 5/15/2014 | | Open |
| General | Technical | Do we need to have an alternative way to get the .xml to the tester in this situation? | John Teeter | 5/15/2014 | | Open |
| General | Technical | Once the flow is broken, it is difficult to get going again. The step testing the validity of the time value is a particular example | John Teeter | 5/15/2014 | | Open |
| General | Editorial | Time evaluation spreadsheet may have a few issues | John Teeter | 5/15/2014 | | Open |
| General | Editorial | Forms consolidation is in order | John Teeter | 5/15/2014 | | Open |
| General | Editorial | replication of test steps (re: login) is magnified by the credentials sharing problem | John Teeter | 5/15/2014 | | Open |
| 2.2 | Editorial | Filling out the 2.2 section (Identification of the test document is a manual step that should be automated to reduce errors. (Auto-Population from the application) | John Teeter | 5/16/2014 | | Open |
| FB 04 | Editorial | Function Block Dependencies and Optional.vs.Required is not clear (FB_04 should have been checked, but was not b/c of user confusion) | John Teeter | 5/16/2014 | | Open |
| | Editorial | PICs document should be merged into the Appilication and have one single, on-line, application flow. (remove error possiblity and focus on single point of data entry) | John Teeter | 5/16/2014 | | Open |
| | Editorial | The validation of having purchased the standard is a manual step that is not easily accomplished. Can we get simpler integration w/o the copy/paste from a PDF? | John Teeter | 5/16/2014 | | Open |
| Login | Editorial | Navigation within the portal under test seems to be error prone. Finding Logout was a problem (it was called sign-out). | John Teeter | 5/16/2014 | | Open |
| 2.3.2.4 | Editorial | Test Step 2.3.2.4 re: what is the time reference for the first interval block. -- The testor has choosen the the time and should not need to ask the testee for that information? | John Teeter | 5/16/2014 | | Open |
| 2.3.2.4 | Editorial | The manual validation of timestamp should be automated. | John Teeter | 5/16/2014 | | Open |
| 2.3.2.4 | Editorial | The testor ability to navigate the xml is not what we should be testing | John Teeter | 5/16/2014 | | Open |
| 2.3.2.4 | Editorial | (@15 minutes testing if the time stamps are valid!) (make that 20 minutes!!)(make that 30 Minutes!!!) | John Teeter | 5/16/2014 | | Open |
| FB 02 | Editorial | The on-line test validator is missing FB_02 (so does not correspond to the PICs) | John Teeter | 5/16/2014 | | Open |
| | Editorial | There is some formating issues with using text "===============" .vs. horizontalRules in the word document that causes miss-steps by the testor. | John Teeter | 5/16/2014 | | Open |
| 2.4.2 | Editorial | 2.4.2 - PII - we have already downloaded the .xml and do not need to do it again. (so the test steps are not being followed - and shouldn't be) | John Teeter | 5/16/2014 | | Open |
| Summary | Editorial | It is difficult to see the "Summary" of what has happened when the testing is completed. | John Teeter | 5/16/2014 | | Open |