Keep payment settings when cloning an event
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 551
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 21
Description
This issue has no description.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue body names no files, tests, or entry points. First locate the event-cloning flow and the payment-settings handling, then clarify which settings must be preserved and verify that cloning retains them without changing unrelated event data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, payments
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100