Manage basic data in frontend #161
Labels
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
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-App-Chronos#161
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In order to move towards creating timetables (#35), we should start by allowing managing of the basic data behind timetables in the UI. These are:
This issue is strictly limited to managing these data, as everything else needs more coplex UI to get relations right.
I am not yet sure whether we should turn this into one page for all basic data (maybe using tabs), or several pages (opinions please, @ZugBahnHof @yuha @hansegucker)
Assigning @lukasw (and @programmtube), but this probably needs a lot of support from someone else.
assigned to @lukasw
created branch
161-manage-basic-data-in-frontendto address this issuementioned in merge request !557
unassigned @lukasw
Closed in favor of new timetable management