mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #142] "Check all" checkbox on logs page does nothing #111
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#111
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 @okoetter on GitHub (Sep 28, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/142
Originally assigned to: @ciur on GitHub.
Bug Description
On the logs page there is a checkbox on the left to "TIME" in the header of the table.
I expect this checkbox means "Check all". But for me it does nothing.
Expected behavior
When I check this checkbox and select "Delete selected logs" I expect all log entries to be deleted.
Desktop (please complete the following information):
@ciur commented on GitHub (Sep 28, 2020):
Hi @okoetter, thank you for reporting the issue!
Funny thing is that I fixed it (click checkbox -> select all issue) in master branch, but I forgot to cherry-pick to stable/1.4.x branch 😁
@ciur commented on GitHub (Sep 29, 2020):
Hi @okoetter, I fixed the issue in release 1.4.5..
@ciur commented on GitHub (Oct 2, 2020):
fix is in master branch (and thus will be available in 1.5.0 release in two weeks).