Phase Planner Page accessed from Feature > Phase.

humansinstitute commented 3 hours ago

Context

Implement a new Phase Planner view allowing Product Managers to create and edit multiple work tickets within a phase. This view integrates with the existing ticket builder system (ref: stakwork/sphinx-tribes-frontend#659) to streamline ticket creation workflow.

Requires ticket: https://github.com/stakwork/sphinx-tribes-frontend/issues/659

Task

Create route /feature/{UUID}/phase/{UUID}/planner
Display Feature and Phase names from API endpoints
Implement "Add Ticket" functionality that creates numbered ticket entries defined in #659)

Outcome

A new Phase Planner page where Product Managers can dynamically add multiple ticket components for batch editing.

Design

UI Layout

See Image below
Ensure current styles are followed.
"Add Ticket" button
Dynamic ticket area

The page will be populated as follows from Tribes endpoints:

Feature Name: r.Get("/{uuid}", featureHandlers.GetFeatureByUuid)
Phase Name: r.Get("/{feature_uuid}/phase/{phase_uuid}", featureHandlers.GetFeaturePhaseByUUID)

Interactions

ON Load page will check for Tickets by Phase UUID.

If tickets are available the page will load each ticket component with data. else ON Load The page will display:
No editable ticket components will be displayed.
The Ticket Builder button - right aligned and levelled with the Ticket Name.
A button Labeled "Add Ticket" On Click of "Add Ticket"
a new editable text box labelled Ticket n where n is +1 the previous ticket will be loaded on the form.
- The component used will be from: https://github.com/stakwork/sphinx-tribes-frontend/issues/659
- Fist "Add Ticket" will be "Ticket 1" then "Ticket 2" and so on. On Click of "Ticket Builder"
Take no action.

Acceptance Criteria