Pilot tests
What the pilot build must prove before any bulk import (section 12). Generated from requirements v0.5 by scripts/gen-requirements.ts; do not edit by hand. Cite one as req:aai-pilot#<ID>.
| ID | Level | Requirement |
|---|---|---|
PIL-01 |
SHALL | An organisation issue field changed on a thin-slice workstream item shows the same value in its workstream project and the programme project |
PIL-02 |
SHALL | Sub-issue progress from two repositories rolls up into the epic in V1 |
PIL-03 |
SHALL | an issue with a note kept off GitHub says so in neutral words only (SEC-02) |
PIL-05 |
SHALL | A blocked label on a feature sets Delivery health to Blocked on the epic within one run of the Action, and the epic appears in V10 |
PIL-06 |
SHALL | Every view in section 8.1 returns the right pilot items |
PIL-07 |
SHALL | The test partner account sets Integration readiness to Validated on a pilot item with no confirmation comment. AUTO-10 adds the validation-exception label and one comment. Running it again adds nothing more. When the Technical Integration Lead adds the confirmation comment, the label is removed |
PIL-08 |
SHALL | Closing a pilot epic as completed sets Programme status to Done through AUTO-03 |
PIL-09 |
SHALL | Closing a pilot item as not planned sets Programme status to Cancelled, and reopening it sets In progress |
PIL-10 |
SHALL | The pinned fields in section 5.3 appear on the issue form for each pilot issue type |
PIL-11 |
SHALL | Charts M1 to M5 show the pilot items correctly, or the report records which cannot be built natively |