Allow managers of indico events to associate an existing room booking to that event
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 551
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 21
Description
Is your feature request related to a problem? Please describe.
I am managing several indico events and room bookings these days. There is a somewhat confusing feature presently:
- In the management of indico events, the 'room booking' tab shows if a room booking is associated to the event, or otherwise allows event managers to book a room. However it does not allow them to associate the event to an existing room booking.
- Similarly existing room bookings display whether they are associated to an existing event. But there is no interface to associate the room booking to an event (or delete the association if it is stale).
- This is confusing because the room booking that is shown has nothing to do with the room where the event is indicated to take place (and which is itself often associated to the possibility to connect that room to zoom). So one may end up having two rooms associated to an event, a visible one (that can be changed) and a somwhat hidden one (that only shows up in some interfaces and can sometimes be added but not changed).
Describe the solution you'd like
One possible solution would be to allow event managers to associate existing room bookings to their event, and similarly to remove existing associations to room bookings which may have become stale or obsolete.
(This would still leave open the issue that there could be two rooms associated to an event, but this may be complex to fix).
Describe alternatives you've considered
A simpler and more radical alternative would be to completely remove the "association" of a room booking to an indico event. As I mentioned, this is NOT the room that shows up as the place where the event takes place, and is in itself of debatable usefulness. It may often just add confusion.
Additional context
None.
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
No files, tests, or entry points are named, so first locate the event-management and room-booking association flows. Define how event managers can associate an existing booking and remove a stale association, then verify both interfaces reflect the change and clarify behavior when two rooms are associated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100