mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #190] Feature Request - Date Formats #151
Labels
No labels
2.1
3.0
3.0.1
3.0.2
3.0.3
3.0.3
3.1
3.2
3.2
3.3
3.5
3.x
Fixed. Waiting for feedback.
Fixed. Waiting for feedback.
UX
Version 2.1 - alpha
XSS
announcement
beta
blocker
bug
cannot reproduce
confirmed
confirmed
critical
demo
dependencies
deployment
detchnical debt
discussion
docker
documentation
donations
duplicate
enhancement
feature request
frontend
fundraising
good first issue
good issue
help wanted
high
implemented
important
improvement
incomplete
invalid
investigation
kubernetes
low
low impact
medium
medium
medium impact
migration from 2.0
migration from 2.1
missing-language
missing-ocr-language
no-activity
note
ocr
outofscope
packaging
performance
popular request
pull-request
pypi
question
raspberry pi
roadmap
search
security
setup
status
task
technical debt
updates
user xp
version 1.4.0 - demo
will be implemented
will not be implemented
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/papermerge#151
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @CorneliousJD on GitHub (Oct 23, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/190
Originally assigned to: @ciur on GitHub.
Is your feature request related to a problem? Please describe.
Right now the date format is DD-MM-YYYY, where a lot of users probably use MM-DD-YYYY, or my preference, YYYY-MM-DD
Describe the solution you'd like
A setting either in the settings file or in webUI (preferred all settings are avaialble in web UI actually! Would make knowing what we can change much easier at a glance)
Thanks in advance, finding this quite easy and pleasing to use so far! :)
@ciur commented on GitHub (Oct 23, 2020):
@CorneliousJD, thank you for well described and to the point feature request.
This issue will be solved in sync with #133