Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
E Expiration Application
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Sigsiu.NET GmbH
  • Expiration Application
  • Issues
  • #5

Something went wrong while setting issue due date.
Closed
Open
Created 5 years ago by Sławek Sikora@SikorReporter
  • New issue

  • Report abuse

  • New issue

  • Report abuse

3rd notifications doesn't count year

Closed

3rd notifications doesn't count year

Looks like 3rd expiration notification doesn't check year of expiration and sent message just when day and month match. So if for example Send Final Message option is set to send message 2 days after, today we have 17.03.2020 and for example entry expiration date is 15.03.2022, expiration message will be send today even if entry will expire after two years.

  1. Oh no!

    You are trying to upload something other than an image. Please upload a .png, .jpg, .jpeg, .gif, .bmp, .tiff or .ico.

    Incoming!

    Drop your designs to start your upload.

Linked issues
0


  • Sławek Sikora @Sikor added Expiration bug new labels 5 years ago

    added Expiration bug new labels

  • Sigrid Suski @TrinitySu assigned to @TrinitySu 4 years ago

    assigned to @TrinitySu

  • Sigrid Suski
    Sigrid Suski @TrinitySu · 4 years ago
    Owner

    Can't reproduce with the current version. The system works always with complete dates.
    Third message is sent for entries where validUntil < today - days after expiration,
    e.g. 2021-09-23 12:37:47 < 2020-09-23 12:51:25

    Please test again with upcoming test version.

    Edited by Sigrid Suski 4 years ago
  • Sigrid Suski @TrinitySu added follow up label 4 years ago

    added follow up label

  • Sigrid Suski @TrinitySu removed new label 4 years ago

    removed new label

  • Sławek Sikora
    Sławek Sikora @Sikor · 4 years ago
    Reporter

    Seems to be working fine now. Checked with 2.0.2

  • Sławek Sikora @Sikor added test passed label and removed follow up label 4 years ago

    added test passed label and removed follow up label

  • Sigrid Suski @TrinitySu closed 2 years ago

    closed

  • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
Please register or sign in to reply
Assignee
Sigrid Suski's avatar
Sigrid Suski
@TrinitySu
Assign to
None
Milestone
None
Assign milestone
None
Time tracking
No estimate or time spent
Due date
None
None
3
Labels
Expiration bug test passed
Assign labels
  • No matching results
  • Manage project labels
Confidentiality
Not confidential
Not confidential

You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

Lock issue
Unlocked
2
2 participants
user avatar
user avatar
Reference:

footer

Legal Notice / Impressum | Data Protection / Datenschutzinformation