Uploaded image for project: 'SimplyE 2.0'
  1. SimplyE 2.0
  2. SIMPLY-2744

Implement Time-Frame Logic for Expiry of Announcements

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Medium Medium
    • 3.0.11cm
    • None
    • None
    • SIMPLY S10 April 28 - May 12, SIMPLY S11 May 12 - May 26, SIMPLY S12 May 26 - June 9, SIMPLY S13 June 9 - June 23, SIMPLY S14 June 23 - July 7, SIMPLY S15 July 7 - July 21, SIMPLY S16 July 21 - August 4, SIMPLY S17 August 4 - 18, SIMPLY S18 August 18 - Sep 1, SIMPLY S19 September 1 - 15, SIMPLY S20 September 15 - 29

      If the person who inputs the Announcement does not specify a time-frame for it to come down, we don't want it to sit in the Authentication document forever. Fortunately, the Authentication document is updated pretty frequently and would refresh this based on what the user puts in. For other cases, we are thinking of making a time-frame of either 6 months or 12 months for cases where this is not specified. This is a product question for Risa Wolf, and once that is ironed out as a requirement, that time frame can be implemented.

            leonardrichardson Leonard Richardson [X] (Inactive)
            andrewshelton Andrew Shelton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: