INDEX :: List of Project Issues

[iPoetDev]

INDEX: List of Project Issues

INVENTORY:

---

DIRECT

Inventory | Workflows | Report

• INDEX :: List of Project Issues #1 INDEX
• FLOW :: Project Repository Setup & Configuration #2 FLOW
• FLOW :: Agile Plan Flow #6 FLOW
• FLOW :: Code Quality Assurance #12 FLOW
• FLOW :: Integration Quality Assurance – CI Workflows (GH Action) - Linting #13 FLOW
• FLOW :: Django Deploy Checks – Scripted #14 FLOW, Deployment
• FLOW :: Architecture Design Flow #19 FLOW, Architecture,
• FLOW :: Deploy Setup  #21 FLOW, Deployment, Configure
• FLOW :: Definition of Done Checklist #25 FLOW, Definition of Done, FINISHED Checklist
• FLOW :: Static Assets into Production #37 FLOW, Static Assets into Production
• FLOW :: UX Design -> UI -> Surface => Django Template Prep #97 FLOW: UX to Django Template Design + TailwindCSS

---

DEFINE

Document | Readme

• DEFINE :: Design System | Software Architecture (Using C4 Model) #7 DEFINE: README
• DEFINE: Readme: 15.0 Deploy #23 DEFINE: 15.0 DEPLOY: Review | Verify?
• DEFINE: Twelve-Factor App methodology | Research & Refine #24 DEFINE: 12 Factor Methodology | Approach
• DEFINE: Dajngo End to End Build to Deploy Flow #32 DEFINE: Django End to End Build to Deploy Flow
• [?] DEFINE: Inspect and Refine GitHub API: Scope, Constraints and Assumptions for the groundwork on Epics, Features, and User Stories #49 DEFINE: Inspect and Refine GitHub API | Revisit as Experience builds

REFINE

Agile Specifications & Requirements: From Idea to UAT

• REFINE: CORE: Web App Landing Page, Forms & Impressum: A Container, Home URL, & Registration for Dash & Do GitHub  #55 REFINE: CORE: App: Landing, Home, Sign Up Flows & Forms, SPA/MPA: Release Plan v0.5
• DEFINE: ACCOUNTS: Django App + Front End: User Registration & Login System #53 REFINE: ACCOUNTS: App: User AAA Flows (Register, Login, Account): Release Plan: v.0.5
• DEFINE :: Single Page Architecture: Dashboard: A single page, multi component, single pane of glass (SPOG) for GitHub Repository reporting and analytics. #56 REFINE: DASH: App:
• REFINE :: Single Page Architecture: Tasker: A single page, multi component, single pane of glass (SPOG) for GitHub Repository Bulk Actions. #57 REFINE: DO (Tasker): App:

PLAN

Sprints | Plan | Flow | Report

• SPRINT :: 01 [5 Days] : "The First Config" : - W/S: 23-JUL-10 | W/E: JUL-14  #3 SPRINT 1
• SPRINT :: 02 & 03 [10/14 Days] : "The Arch n Deploy": - W/S: 23-JUL-17 | W/E: JUL-28 #DESIGN #4 SPRINT 2 / 3 (Two Weeks)
• SPRINT PLAN :: 04 [5 Days] : "For Agile n Test" : - W/S: 23-JUL-31 | W/E: AUG-04 #? #5 SPRINT 4
• SPRINT PLAN :: 05 [5 Days]: Release: v0.5: “Core + Accounts: C4 Models to Data Models: Logical Design & Structures”: - W/S: 23-AUG-07 | W/E: 23-Aug-11/13 #? #63 SPRINT 5
• SPRINT PLAN:: 07 [7 Days]: Release: v0.5: “Core + Accounts: UI Surface & Forms/Templates”: - W/S: 23-AUG-21 | W/E: 23-Aug-27 #64 SPRINT 6
• SPRINT PLAN :: 09 [7 Days]: Release: v0.5: “Core + Accounts: Integrate, Test, Deploy”: - W/S: 23-SEP 11 | W/E: 23-SEP-16 #65 SPRINT 7
• 8
• 9
• 10

STORY

User Stories

Release: v0.5

• New Visting User: As a new visiting user to the Dash and Do GitHub website, and web app, I want to arrive on a landing page, a home page, which immediately gives me strong impression, clues and calls to action of purpose, identity, registration, and login. (See related component stories below). #81
• Newly Visting User's URL: As a new visiting user to the Dash and Do GitHub website, and web app, I want to have a clearly memorable and easy to use URL as a domain name and as a brand identity so that I can remember the website and come back to it on a repeated basis. #82
• New Registration User Story: As a prospective user of the Dash and Do GitHub web app, I want to create an account by registering with the service so that I can be authorised to access the web service and have a newly created login (username and password). #54
• Confirm Registered User Story: As a prospective user of the Dash and Do GitHub web app, I want to receive a confirmation message by having registered with the service so that I can be verified and authenticated for authorisation and access to the web service and or be automatically logged in. #66
• Existing Login User Story: As an existing user, I want to find the login form, and have an option to remember me for next visit, as well as have an option to reset my password, so that I can successfully login. #67
• Unsuccessful Login Existing User Story: As an existing user, I want to have a good user experience when I am unsuccessfully logging and have good notifications so that I have an improved user experience and increases my chance to login successfully. #68
• Forgets Password User Story: As a forgetful user of the Dash and Do GitHub web app, I want to be able to reset my password and have a secure option to reset the password by an URI. #69
• Verify Password Reset User Story: As a password resetting user of the Dash and Do GitHub web app, I want to be verified my newly reset password and have a secure option to reset the password by an URI. #70
• Set + Persist Session User Story: As a returning user of Dash and Do GitHub web app, I want to be immediately logged into my account so that I do not have to login and reuse my password on every visit, by using a remember check box on login (opt in). #71
• New User Login Story: As newly registered user of Dash and Do GitHub web app, I want to find my profile and have an easy user-friendly experience to locate and start my profile. #83
• Unauthenticated User Login Story: As an unauthenticated user, I want to not be able to restrict content and not have access to sensitive functionality so that all users have trust, confidence, integrity and availability in the web app and service #84
• Unauthorised/access User Login Story: As an unauthorised user, I want to not be able to restrict content and not have access to sensitive user data so that all users have trust, confidence, integrity and availability in the web app and service #85
• User Session Authorised Story: As an authenticated user of Dash and Do GitHub web app, I want to authorised to access and persist this trusted state across one or more visits. #73
• User Session Forgets Story: As an authenticated user of Dash and Do GitHub web app, I want to have my session forgotten and the current session destroyed so that I have login and reauthenticate. #74
• User Profile Access Story: As an authenticated user of Dash and Do GitHub web app, I want to access and read my user profile. #75
• User Profile Update Story: As an authenticated user of Dash and Do GitHub web app, I want to be able to edit and modify my user profile details. #76
• User Profile Deletion Story: As an authenticated user of Dash and Do GitHub web app, I want to be able to delete and remove my user profile data. #77
• User Account Removal Story: As an authenticated user of Dash and Do GitHub web app, I want to be able to finally delete my account. #78
• Admin User Profile Access Story: As an authorised administrator user (role) of Dash and Do GitHub web app, I want to access and read all user profile in a specific admin user interface (comes de-facto with Django). #79
• Admin User Profile Update Story: As an authorised administrator user (role) of Dash and Do GitHub web app, I want to create, edit, modify, and remove user profiles in a specific admin user interface (comes de-facto with Django). #80

Dev Stories

• STORY: As a Developer, I want to set and assure Code Quality as a Standard #16 STORY, Code Standards
• STORY :: Architecture: As a Developer, I want to design a system and sub system level model #18 STORY, System Design
• STORY: As a 12 Factor App Developer, I want to have one Codebase & many Deploys #26 STORY, 12 Factor, (I) Codebase, Many Idempotent Deploys
• STORY: As a 12 Factor App Developer, I must explicitly declare all isolated Dependencies (II) for Python 3.11 #27 STORY, 12 Factor, (II) Dependencies, Python 3.11
• STORY: As a 12 Factor App Developer, I must explicitly declare all isolated Dependencies (II) for JavaScript or NodeJs #28 STORY, 12 Factor, (II) Dependencies, JavaScript/NodeJS 20.0
• STORY: As a 12 Factor App Developer, want a Backing Service (IV), i.e. a Relational Database, which is a loosely coupled attachable resource #29 STORY, 12 Factor, (III) Backing Services, i.e. Relational Database
• STORY: As a 12 Factor App Developer, I want to store Config in the Environment (III) #30 STORY, 12 Factor, (IV) Config, Environmental Variables, Connection Strings, Credentials/Secrets, Canonical Values
• STORY: As a 12 Factor App Developer, I need to run Admin Process (XII) tasks as once-off (standalone) processes #31 STORY, 12 Factor, XII), Admin Tasks, Django migrations, and manage scripts

FEATURES

• FEAT :: VIEW: PUBLIC: index.html Page: All Users and Unauthenticated Users: i.e. the New Visitor, Unregistered and Not Logged In Visitor || index.html <= page.html #98
• FEAT :: VIEW: PRIVATE: index.html Page: All Users and Authenticated Users: i.e. the Returning Visitor, Registered and Logged In Visitor (with Actve Session) || index.html <= page.html #99
• FEAT :: VIEW: PUBLIC: Email Verification & verify.html <= simple.html #100
• FEAT :: VIEW: PUBLIC: Contact Email & Contact Form: All Users (Public Users and Private Users) || index.html <= page.html #101
• FEAT :: VIEW: PUBLIC: New User Registration & Sign Up Form: Public Users || index.html <= page.html #102
• FEAT :: VIEW: PUBLIC: Existing User Access & Login Up Form: Public Users || index.html <= page.html #103
• FEAT :: VIEW: PUBLIC: Existing User Reset Passwords, Reset Password Form & Verify Reset: Public Users: || verify.html <= simple.html #104

DESIGN

BUILD

Fix

TEST

CHECK

• CONFIG :: Heroku Production Checklist #20 CHECKLIST, Heroku Production

DEPLOY

---

[iPoetDev]

Updated

• REFINE for Agile Specifications and Requirements
• Added Sprint 5, 6, 7 with placeholders for 8,9 & 10
• STORY for
  • Release v0.5
• Moved Dev Stories into a sub section by block quotes as minor-isation effort.