Gig cloning
- Dominant language
- TypeScript
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to be able to "clone" gigs, so the secretary can create the next iteration of a regular gig (e.g. an annual charity gig) without having to worry about selecting all of the details. This could copy the name, venue, timings, summary and clients, and set it to an enquiry with the quote given on the current date.
Very much a nice-to-have rather than an essential feature. It would also be useful e.g. during a pandemic when many gigs are being rescheduled and the details are largely unchanged.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the existing gig creation flow and the fields used for name, venue, timings, summary, clients, status and quote date. Done means a new gig can be created from an existing one with those details copied, its status set to an enquiry, and its quote dated to the current day.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100