Skip to content

Issue with dates #26

@ktecho

Description

@ktecho

Hi,

I'm european, so we use the dd/mm/aaaa (which is dd/mm/yyyy in spanish) format for dates. In the forms, I've introduced this, so it seems like the field is localized:

Image Image

I've introduced this dates using that field and I get the dates like this. It's in american format, so it could also be localized here, but anyways. I can guess it's always December:

Image

So for the last 3, it saved it like european dates, because you cannot have the month 15 or 25. But for the first one, as it's possible to have day 12 of month 10, it saved it in american format, so if I edit the option again, now I get this:

Image

So it's wrong, because it was an operation opened in December, not October. And it's a mess, because it thinks that the option is not closed, which is weird, because either 12/10 or 10/12 should be expired already, but it's not:

Image

If I can help you test something, just tell me.

Edit: Wait, maybe this last problem is because it appears as opened because you have to close them manually? I just put the close date and now it dissapeared from there. Shouldn't the app auto-close the options after the expiry date?

If that's correct, then maybe everything is ok, and the only think to fix (improve?) would be show the dates in european format also in the tables depending on the locale info.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions