Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider creating a job to remove a session from the project automatically when it gets closed #30

Open
Tracked by #23
tidoust opened this issue Jun 27, 2023 · 1 comment
Open
Tracked by #23

Consider creating a job to remove a session from the project automatically when it gets closed #30

tidoust opened this issue Jun 27, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@tidoust
Copy link
Member

tidoust commented Jun 27, 2023 •
edited
Loading

This should be low priority.
@tidoust tidoust mentioned this issue Jun 27, 2023
Closed
27 tasks
@tidoust tidoust changed the title Job to remove a session from the breakout session project when it gets closed Consider creating a job to remove a session from the project automatically when it gets closed Jun 27, 2023
@tidoust tidoust added the enhancement New feature or request label Jul 4, 2023
@tidoust
Copy link
Member Author

tidoust commented Sep 6, 2023 •
edited
Loading

To clarify, this includes:

  • removing the session from the project
  • canceling the calendar entry
  • removing references to the issue in the conflict section of other issues
  • re-validating sessions that got updated (if there was a real conflict due to the now closed issue, this conflict should be gone)

@tidoust tidoust mentioned this issue Sep 6, 2023
Closed
tidoust added a commit that referenced this issue Jan 17, 2024
@tidoust
Maintain one calendar entry per plenary meeting
9d2effd 
This rewrites the calendar maintenance logic to add support to plenary
meetings.

Plenary meetings make the logic more complex because it breaks the 1-to-1
mapping that existed between sessions and calendar entries. The logic now needs
to handle corner cases such as:
- a session that used to be a breakout and that becomes a plenary session.
- a session that used to be a plenary session that becomes a breakout session.
- a session moved from one plenary meeting to another.

As part of the update, the logic now correctly handles canceling/deletion of
a calendar entry when needed, meaning when session now needs to be associated
to another calendar entry, or when the session is no longer associated with a
slot. FWIW, that is not enough to support the case when a session issue is
closed (see #30): we need a job that reacts on issue closure.
@tidoust tidoust mentioned this issue Jan 17, 2024
Merged
tidoust added a commit that referenced this issue Jan 17, 2024
@tidoust
Maintain one calendar entry per plenary meeting (#76)
812595c 
This rewrites the calendar maintenance logic to add support to plenary
meetings.

Plenary meetings make the logic more complex because it breaks the 1-to-1
mapping that existed between sessions and calendar entries. The logic now needs
to handle corner cases such as:
- a session that used to be a breakout and that becomes a plenary session.
- a session that used to be a plenary session that becomes a breakout session.
- a session moved from one plenary meeting to another.

As part of the update, the logic now correctly handles canceling/deletion of
a calendar entry when needed, meaning when session now needs to be associated
to another calendar entry, or when the session is no longer associated with a
slot. FWIW, that is not enough to support the case when a session issue is
closed (see #30): we need a job that reacts on issue closure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tidoust