We're updating the issue view to help you get more done. 

Incorrect Start Date and Expiry Date behavior for system notification

Description

While checking OLMIS, I noticed the following:

  1. After removing the Start Date and Expiry Date, the message is created and the dates are entered automatically.

  • Reproduction steps:

  • Go to Administration > System Notification and click the "Add System Notification" button.

  • Fill in all fields, remove Start Date and Expiry Date and click the "Add System Notification".

  • The message is created and fields with dates are filled out.

2. While editing a message, one can't delete Expiry Date (and can't remove Start Date to).

  • Reproduction steps:

  • Go to Administration > System Notification and click the "Edit" button next to any message.

  • Remove Expiry Date and click the "Update System Notification".

  • Click the "Edit" button next to the same message.

  • Field with Expiry Date is still filled in (the same issue occurs with Start Date).

3. Due to the fact that the dates sign up automatically, the message "System notification start date should be before expiryDate." appears when I choose today's date as Expiry Date and then delete it.
And in this message "expiryDate" should be written "Expiry Date".
Please take a look at Expiry Date2.gif

 

Environment

None

Status

Assignee

Paulina Buzderewicz

Reporter

Joanna Szymańska

Labels

Story Points

3

Time tracking

24h

Epic Link

Components

Sprint

None

Fix versions

Affects versions

3.7

Priority

Major