Sprint details view should have auto population of data.
Entry point of data fetch will be navigation address /sprint/:idwhere :id is the name of the sprint. This will be used to fetch the sprint data from dynamo DB, maybe a correlating ID would be easier. Something like sprint name -> correlating ID -> fetch from other tables. Correlation ID could be avoided if the name for a sprint is made to be unique.
Open questions
Is correlation ID needed?
Is DynamoDB the best place to have something for validating for a unique name? Would simple documents in S3 be better?
Sprint details view should have auto population of data. Entry point of data fetch will be navigation address
/sprint/:id
where:id
is the name of the sprint. This will be used to fetch the sprint data from dynamo DB, maybe a correlating ID would be easier. Something like sprint name -> correlating ID -> fetch from other tables. Correlation ID could be avoided if the name for a sprint is made to be unique.Open questions