(Program) Lock time periods for new events per program

Registered by Lars Helge Øverland on 2016-08-17

Add support for locking time periods for new events and modifications of existing events per program.

Introduce two properties on Program:

- "expiryDays" (int)
- "expiryPeriodType" (PeriodType)

The expiryDays property will control the number of days for which it should be allowed to add and modify events for the program. The expiryPeriodType property defines the period type which controls the basis for the number of expiry days. The number of expiry days is hence defined as the end date of the period of the expiry period type for which the period is within, plus the number of expiryDays defined for the program.

Example: Expiry days is 7. Expiry period type is Monthly. Given the period of March 2016. This period will be locked 7 days after the end date of March 2016, which is April 7. Hence, after April 7, no new events or modifications of existing events can take place for events registered before April 7.

Blueprint information

Status:
Complete
Approver:
Lars Helge Øverland
Priority:
Medium
Drafter:
Lars Helge Øverland
Direction:
Approved
Assignee:
Abyot Asalefew Gizaw
Definition:
New
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon 2.25
Started by
Abyot Asalefew Gizaw on 2016-09-23
Completed by
Abyot Asalefew Gizaw on 2016-09-23

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.