Course names should be used more prominently #252

New issue

Open

opened 2026-09-15 20:37:34 +02:00 by magicfelix · 0 comments

magicfelix commented 2026-09-15 20:37:34 +02:00

Member

Copy link

Currently, only subject, teacher, room (and group, because you view a timetable for a specific group) are displaed. It would be useful to have the course name visible in lesson management and timetable display. At least as a configurable option, to enable it if desired.

Use case: There may be multiple courses with the same subject and generally offered for the same group(s). For example, Math 1 and 2, different levels, but because the children are free to choose were to go, it cannot be distinguished by the group the courses have assigned, because both have the same group.

Currently, only subject, teacher, room (and group, because you view a timetable for a specific group) are displaed. It would be useful to have the course name visible in lesson management and timetable display. At least as a configurable option, to enable it if desired. Use case: There may be multiple courses with the same subject and generally offered for the same group(s). For example, Math 1 and 2, different levels, but because the children are free to choose were to go, it cannot be distinguished by the group the courses have assigned, because both have the same group.

magicfelix added the

source

customer::fsmw

type

feature

workflow

discussing

labels 2026-09-15 20:37:35 +02:00

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

aleksolotl-checks

check/update-pyproject-toml

check/update-tox-ini

86-adapt-to-drop-of-calendareventbatchcreatemixin-in-core

check/update-eslint-rc-js

77-job-failed-356115-due-to-non-existing-render_progress_page

migrate-to-uuid

release/0.1.0.dev6

release/0.1.0.dev5

13-fields-in-course-planning-should-be-as-small-as-possible

52-always-create-tccs-and-use-them-as-single-uniform-inerface-during-planning

4-lock-access-for-editing-of-validity-range-after-validity-range-changes-to-published-status

release/0.1.0.dev2

12-select-in-course-planning-should-not-use-all-groups-per-default

31-add-carry-over-feature-for-lessons-and-supervisions

fix-chronos-migration-dep

tmp/drop-sites-and-fix-migration-deps

2-add-model-for-planning-of-courses-dependend-on-validityrange

manage-holidays

3.0.0

2.0.2

2.0.1

2.0.0

1.0.1

1.0.0

0.1.0.dev6

0.1.0.dev5

0.1.0.dev4

0.1.0.dev3

0.1.0.dev2

0.1.0.dev1

0.1.0.dev

Labels

Clear labels   

Security

  

TeX

Needs LaTeX template

  

auto-update

  

board

done

  

board

ready

  

board

todo

  

check

delete-eslint-rc-js

  

check

update-builddeps-package-json

  

check

update-eslint-rc-js

  

check

update-gitignore

  

check

update-merge-request-template

  

check

update-prettier-ignore

  

check

update-pyproject-toml

  

check

update-renovate-json

  

check

update-tox-ini

  

part

backend

Backend (view code, models, logic, etc.)

  

part

ci

  

part

docs

Issue or addition to the documentation

  

part

frontend

Frontend (templates, etc.)

  

part

i18n

Translation or internationalisation issue

  

part

non-technical

Non-technical (policy, maintenance, etc.) issue or discussion

  

part

packaging

Issue concerning the packaging of AlekSIS and components

  

prio

1

Priority High

  

prio

2

Priority Medium

  

prio

3

Priority Low

  

release-mr-5.x

  

size

large

  

size

medium

  

size

small

  

source

customer

Requested by a customer or affiliated user

  

source

customer::fsmw

  

source

customer::fss

  

source

customer::teckids

  

source

downstream

Issue or merge request from other projects using AlekSIS or parts of it

  

type

breaking

  

type

bug

Bug

  

type

feature

New feature

  

type

refactoring

  

workflow

blocked

Issue is blocked by another issue

  

workflow

confirmed

The bug is reproducible and will be fixed

  

workflow

current-todo

  

workflow

discussing

Needs to be discussed before implementation

  

workflow

new-app

Requires new AlekSIS app, which has to be created

  

workflow

wontfix

The bug is not reproducible or the feature was decided against

  

source::aleksolotl

No labels

Security

TeX

auto-update

board

done

board

ready

board

todo

check

delete-eslint-rc-js

check

update-builddeps-package-json

check

update-eslint-rc-js

check

update-gitignore

check

update-merge-request-template

check

update-prettier-ignore

check

update-pyproject-toml

check

update-renovate-json

check

update-tox-ini

part

backend

part

ci

part

docs

part

frontend

part

i18n

part

non-technical

part

packaging

prio

1

prio

2

prio

3

release-mr-5.x

size

large

size

medium

size

small

source

customer

source

customer::fsmw

source

customer::fss

source

customer::teckids

source

downstream

type

breaking

type

bug

type

feature

type

refactoring

workflow

blocked

workflow

confirmed

workflow

current-todo

workflow

discussing

workflow

new-app

workflow

wontfix

source::aleksolotl

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

aleksis/AlekSIS-App-Lesrooster#252

No description provided.