Bug 53905 – Collecting projects does not match documentation

Bug 53905 - Collecting projects does not match documentation


Summary:	Collecting projects does not match documentation

Status:	RESOLVED DUPLICATE of bug 30319

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Distribution
Version:	UCS@school 4.4
Hardware:	Other Mac OS X 10.1

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2021-10-14 09:42 CEST by Ole Schwiegert
Modified:	2021-10-14 09:56 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.103
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 Ole Schwiegert

2021-10-14 09:42:59 CEST

The documentation states:

Die eingesammelten Dateien werden im Heimatverzeichnis der Lehrkraft abgelegt, die das Verteilungsprojekt erstellt hat. Dies erfolgt unabhängig davon, welche Lehrkraft das Einsammeln der Dateien auslöst!

The product tests state:

Einsammeln, Einsehen und Bearbeiten kann man nur seine eigenen Projekte

The actual behavior is:

Anyone using the UMC module can trigger the collection of projects, also one that are not owned. The results are collected into the home folder of the collecting user, not the one who created (better wording would be owning) it.

I am not sure right now if this is simply a case of doc not matching the behavior or if this behavior is actually undesired.

-- I did not test this yet, but I would strongly assume this is not a regression from 4.4, but shows the same behavior.

Comment 1 Ole Schwiegert

2021-10-14 09:51:20 CEST

This behavior is the same as in 4.4

I retag the milestone to reflect that

--> No regression for 5.0

Comment 2 Ole Schwiegert

2021-10-14 09:56:35 CEST


*** This bug has been marked as a duplicate of bug 30319 ***