Bug 40063 – App Reporting should not depend on UCR variables

Bug 40063 - App Reporting should not depend on UCR variables


Summary:	App Reporting should not depend on UCR variables

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	App Center
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	App Center maintainers
QA Contact:

URL:
Keywords:

Depends on:	38951 38953 40062
Blocks:
	Show dependency tree / graph

Reported:	2015-11-23 07:01 CET by Dirk Wiesenthal
Modified:	2019-01-03 07:18 CET (History)
CC List:	6 users (show)

See Also:
What kind of report is it?:	Development Internal
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 Dirk Wiesenthal

2015-11-23 07:01:35 CET

Currently, the App reporting Tool reads some UCR variables to know which objects to count.

The App Center Sets These variables during registration of an App. It would be easier to read data directly from the Apps, not UCR.

This also allows the not-so-error-prone changing of These variables in the ini file.

+++ This bug was initially created as a clone of Bug #40062 +++

univention-appreport should be Part of UCS 4.1.

Currently the Source directory is empty.

Comment 1 Stefan Gohmann

2019-01-03 07:18:36 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

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