Bug 48120 – Required format to import classes is not very usable

Bug 48120 - Required format to import classes is not very usable


Summary:	Required format to import classes is not very usable

Status:	RESOLVED WONTFIX

Product:	UCS@school
Classification:	Unclassified
Component:	Import scripts
Version:	UCS@school 4.3
Hardware:	Other Mac OS X 10.1

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-11-08 11:37 CET by Michel Smidt
Modified:	2023-06-23 13:02 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michel Smidt 2018-11-08 11:37:23 CET

The Required format to import classes is not very usable:
"Gruppen bzw. Klassen als String im Format schule1-1A,schule1-2B,schule2-1A oder als Python dictionary: {"schule1": ["1A", "2B"], "schule2": ["1A"]}."

In almost all cases the input data only contains a list of classes without the school name (e.g. "1A,2B,4D").
In this cases the classes must be set only on the import school and it is very costly to change this every time.

Comment 1 Daniel Tröder

2018-11-08 11:59:00 CET

Please explain the feature request a bit more.
How should the behavior be?
In which circumstances?

Comment 2 Jan-Luca Kiok

2023-06-23 13:02:15 CEST

This issue has been filed against UCS 4.3.

UCS 4.3 is out of maintenance and UCS components may have vastly changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen this issue. In this case please provide detailed information on how this issue is affecting you.