View Issue Details

IDProjectCategoryView StatusLast Update
0000931Main CAcert Websiteweb of trustpublic2013-01-18 00:12
Reporterabheiden Assigned To 
PrioritylowSeverityfeatureReproducibilityhave not tried
Status closedResolutionduplicate 
Fixed in Version2013 Q1 
Summary0000931: Date of assurance in future don't throw any exception
Description256084 2012-13-12 Atona Çodelu 2 "Mein Haus", Sindelfingen Administrative Increase
TagsNo tags attached.
Reviewed by
Test Instructions


related to 0001023 needs workEva Consolidate changes into the Assure Someone page 
related to 0000870 closed My Details - My Points show bugus time stamp 
related to 0000801 closed Date of assurance should be in user's timezone 
related to 0000583 closed "Assure Somebody" allows future assurance dates 
related to 0001014 closedINOPIAE Remove the system of automatically adding a timestamp 
related to 0001137 closedBenBE Record the CCA acception for entering an assurance 



2011-06-14 11:18

administrator   ~0002031

Is this an issue with the manager ( or the WebDB (i.e.


2011-06-25 07:47

reporter   ~0002064

I put this data in frontend system (WebDB).
The date field accepts all kinds of input e.g. text and numbers.


2011-07-08 11:13

administrator   ~0002106

The date you enter in the assurance form is just a note to you when the assurance happened and you are responsible for filling in sensible data. The data base has it's own internal time stamp to keep track of when the assurance was entered in the system although it is never displayed currently.

We could provide something like a date picker so only dates of a certain format are allowed and then we could do some testing for sensible values but that is rather low priority right now

Werner Dworak

2012-12-24 17:12

updater   ~0003559

It is not easy. On the one side, there have been good reasons to allow free text and we should keep this. But on the other side, it would help if there were a warning (not a blocking!) "do you really want to enter this?" if the entered text does not resolve to a valid date in the past.


2013-01-18 00:02

updater   ~0003698

the date check is included in bug

Issue History

Date Modified Username Field Change
2011-05-07 17:25 abheiden New Issue
2011-06-14 11:18 NEOatNHNG Note Added: 0002031
2011-06-14 11:18 NEOatNHNG Assigned To => NEOatNHNG
2011-06-14 11:18 NEOatNHNG Status new => needs feedback
2011-06-14 11:22 NEOatNHNG Category =>
2011-06-25 07:47 abheiden Note Added: 0002064
2011-06-25 07:47 abheiden Status needs feedback => needs work
2011-06-26 20:21 NEOatNHNG Project => Main CAcert Website
2011-06-26 20:21 NEOatNHNG Category => General
2011-06-26 20:22 NEOatNHNG Reporter abheiden => aboernig
2011-06-26 20:22 NEOatNHNG Category General => web of trust
2011-06-26 20:23 NEOatNHNG Reporter aboernig => abheiden
2011-07-08 11:13 NEOatNHNG Note Added: 0002106
2011-07-08 11:13 NEOatNHNG Status needs work => confirmed
2011-07-08 11:14 NEOatNHNG Priority normal => low
2011-07-08 11:14 NEOatNHNG Severity minor => feature
2012-12-24 17:12 Werner Dworak Note Added: 0003559
2012-12-27 05:39 Werner Dworak Relationship added related to 0001023
2012-12-27 05:39 Werner Dworak Relationship added related to 0000870
2012-12-27 05:40 Werner Dworak Relationship added related to 0000801
2012-12-27 05:41 Werner Dworak Relationship added related to 0000583
2012-12-27 05:43 Werner Dworak Relationship added related to 0001014
2013-01-18 00:02 INOPIAE Note Added: 0003698
2013-01-18 00:02 INOPIAE Status confirmed => closed
2013-01-18 00:02 INOPIAE Assigned To NEOatNHNG =>
2013-01-18 00:02 INOPIAE Resolution open => duplicate
2013-01-18 00:02 INOPIAE Fixed in Version => 2013 Q1
2013-01-18 00:12 INOPIAE Relationship added related to 0001137