Skip to content

Some script parameters marked as required incorrectly #22

Description

@AndrewBWS

When configuring the longoverdue cron, several values are marked as required when they should not be. The cron will fail if no value is provided for --l, but does not truly require values for:

  • --c
  • --maxdays
  • --category
  • --skip-categories
  • --list-categories
  • --library
  • --skip-library
  • --itemtype
  • --skip-itemtype
  • --skip-lost-value

The runreport cron similarly has several values marked as required when they should not be.
I've not evaluated all of the other crons for this, but it seems that work is required.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions