Time Range Sidebar: Context menus

[Joachim Kohlhammer]

Hi all,

especially before digging deeper into the implementation of seasons, phases and events, it was unclear to me how these items can be nested. The menus (both burger and right click) are context sensitive but don't help too much about what will be added where:

Right clicking a phase allows to add a season, event or phase, all of those on the same level in the menu but result in actions on different levels. The season will be added to the toplevel, phases and events as siblings of the current phase.

To improve the situation, I have the following proposal:

# Context menus
## User defined absolute Season
Edit Season...
Delete Season
──────────────
Add Phase...
Add Event...
──────────────
Add Season...

## Phase (example: nested in Season "2025")
Edit Phase...
Delete Phase
──────────────
Add Phase to "2025"...
Add Event to "2025"...

## User defined relative Season
Edit Season...
Delete Season
──────────────
Add Phase... (grayed out)
Add Event... (grayed out)
──────────────
Add Season...

## Predefined Season
Edit Season... (grayed out)
Delete Season (grayed out)
──────────────
Add Phase... (grayed out)
Add Event... (grayed out)
──────────────
Add Season...

## Empty space
Add Season...

# Burger menu
## Selected: User defined absolute Season
Same as context menu above

## Selected: Phase
Same as context menu above plus:
──────────────
Add Season...

## Selected: User defined relative Season
Same as context menu above

## Selected: Predefined Season
Same as context menu above

## Selected: Nothing
Same as empty space context menu above

In my view, this would make the scope of the executed action clearer. Feedback is welcome!

I am aware this will require minor adaptions to the translations. But especially adding the ellipsis to all affected items could be done by me, reducing that effort for others.

Cheers, Joachim

[Ale Martinez]

Hi Joachim, this is a much needed normalization and fully agree with your approach, but I am not sure about nested phases (phases within phases) since I have not tried to use them, do they work now or is something you plan to add?

[Joachim Kohlhammer]

Ale Martinez schrieb am Samstag, 17. Januar 2026 um 12:48:23 UTC+1:

Hi Joachim, this is a much needed normalization and fully agree with your approach, but I am not sure about nested phases (phases within phases) since I have not tried to use them, do they work now or is something you plan to add?

Currently phases cannot be nested: When creating a phase, it always belongs directly to a season. If you don't see need for nested phases, I will keep the status quo and only update the menus.

[Ale Martinez]

Nevermind, I misunderstood the fragment:

>## Phase (example: nested in Season "2025")
>Edit Phase...
>Delete Phase
>──────────────
>Add Phase to "2025"...
>Add Event to "2025"...

without realizing the Phase was added to the parent season, it's ok for me, sorry.