Bug 48933 - univention-admin-diary-entry-create creates "null" entry when invoked without command line arguments
Summary: univention-admin-diary-entry-create creates "null" entry when invoked without...
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: Admin Diary
Version: UCS 4.4
Hardware: Other Linux
: P5 minor
Target Milestone: ---
Assignee: UCS maintainers
QA Contact: UCS maintainers
URL:
Keywords:
Depends on: 48476
Blocks:
  Show dependency tree / graph
 
Reported: 2019-03-09 13:48 CET by Philipp Hahn
Modified: 2024-06-27 12:09 CEST (History)
1 user (show)

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?: 4: Will affect most 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.137
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Customer ID:
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 Philipp Hahn univentionstaff 2019-03-09 13:48:14 CET 
When /usr/bin/univention-admin-diary-entry-create in invoked without giving any command line argument, it simply prints a UUID and generated an entry in the backend named "null". Clicking on that entry does NOT open any detail page.

The command probably should do nothing if no message is provided. Make option "message" required?
(please read the "Note" from <https://docs.python.org/2/library/argparse.html#required>)
Comment 1 Jan-Luca Kiok univentionstaff 2024-06-27 12:09:42 CEST 
This issue has been filed against UCS 4.4.

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

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