ⓘ How the train works

• Dev — create a solution, add Jira tickets, set a requested deploy date, record a Dev sign-off.
• Submit for UAT (Dev) is blocked until there's a Dev sign-off, a requested date, and at least one ticket. It freezes the tickets and notifies the RTE.
• Mark deployed to UAT (RTE) moves it across, stamps the RTE + date, and notifies the team. A UAT sign-off is then recorded by the tester.
• Submit for Prod (Dev) needs the UAT sign-off; then Mark deployed to Prod (RTE) stamps the RTE + date and notifies the team.
• In Prod, verify each ticket. Once every ticket is checked, anyone can Close the solution — it moves to the Closed bucket.
• State auto-saves to this browser. Use Export to share the canonical copy or park it in SharePoint.