Overview
A ticket to track our status releasing PlaceCal v1.0. This work will be completed across multiple milestones and tickets and this aims to keep an overview of the project. This ticket is to focus on the absolute have to haves -- let's focus on making what we have right now work reliably and well.
Overall this core funcionality is all reviewing the basic create, read, update and delete commands for our 3 current user groups and making sure they're all watertight and nice to use (citizens, partners, and organisers)
This kind of ticket might be a terrible idea but I think i prefer to keep this thinking in the repo and not notion.
Tech Debt
Citizens
Partners
Organisers / Commissioners
For now these are the same thing - lets make both work to a minimum standard first, and look at commissioner-specific rights later on.
Bonus features
Low hanging fruit that could be seen as part of getting wider adoption of the idea as a whole but are deffo not 100% needed technically. I guess you can think of this as ecosystem stuff - like if we are selling an ecosystem then we need at least a minimal thing to point at about what the ecosystem looks like to make our USP clearer that we're not just about selling another app. It helps these map on to our user groups too!
Overview
A ticket to track our status releasing PlaceCal v1.0. This work will be completed across multiple milestones and tickets and this aims to keep an overview of the project. This ticket is to focus on the absolute have to haves -- let's focus on making what we have right now work reliably and well.
Overall this core funcionality is all reviewing the basic create, read, update and delete commands for our 3 current user groups and making sure they're all watertight and nice to use (citizens, partners, and organisers)
This kind of ticket might be a terrible idea but I think i prefer to keep this thinking in the repo and not notion.
Tech Debt
Citizens
Partners
Organisers / Commissioners
For now these are the same thing - lets make both work to a minimum standard first, and look at commissioner-specific rights later on.
Bonus features
Low hanging fruit that could be seen as part of getting wider adoption of the idea as a whole but are deffo not 100% needed technically. I guess you can think of this as ecosystem stuff - like if we are selling an ecosystem then we need at least a minimal thing to point at about what the ecosystem looks like to make our USP clearer that we're not just about selling another app. It helps these map on to our user groups too!