Bug 43477 - Add option to app provider notification for immediately sending after action was triggered by user
Add option to app provider notification for immediately sending after action ...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: App Center
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: App Center maintainers
App Center maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2017-02-02 09:50 CET by Nico Gulden
Modified: 2020-07-03 20:56 CEST (History)
2 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

Note You need to log in before you can comment on or make changes to this bug.
Description Nico Gulden univentionstaff 2017-02-02 09:50:29 CET
App providers are notified on the next day upon installation, updates and uninstallation of apps. Once in a while there is the request by app providers to receive the notification immediately after the action took place. They'd like to send out a demonstration or test key to those users. The notification on the next day has a way too high delay for this use case.

We should think about changing this behavior. Idea:
* Default: Notification on the next day. This is valid for most of the app providers.

* Setting: App providers can define in the .ini file that they want an immediately notification. They can set it optionally.
Comment 1 Alexander Kläser univentionstaff 2017-02-03 15:04:01 CET
We could also just send out the notifications by default immediately... this would safe the extra logic of differing between the two options ;) .
Comment 2 Ingo Steuwer univentionstaff 2020-07-03 20:56:18 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have 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 it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.