mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #155] [Feature] Undo Function #122
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#122
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 @b0mb on GitHub (Oct 10, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/155
Originally assigned to: @ciur on GitHub.
It would be great implementingan undo function to papermerge.
especially when cutting documents something goes wrong very fast. ^^
@ciur commented on GitHub (Oct 10, 2020):
Hi @b0mb,
thank you for opening this ticket. The "Undo" function contradicts versioning feature (or stated in other words - is a special case of versioning). Let me explain with an example: let's say a document Doc1 has 2 pages. If you cut/delete Doc1 second page - document's version will be incremented i.e. doc1 will have now version 2.
Now, question: if you click/choose "Undo" what should happen ? The usual undo feature like most of users are used to - should revert document to previous state - doest it mean reverting back to version 1 ? But that will contradict the whole versioning thing.
Document management system usually rely on versioning. So, the "Undo feature" is exercised by "versioning" - what I mean, if you want to "Undo" you will need to revert to a previous version.
Versioning is not yet there, but it is something which I plan to implement. Because of argument I described above - I think "Undo Funcion" is just another name for "versioning" feature.
@b0mb, what do you think ?
@b0mb commented on GitHub (Oct 10, 2020):
Hi Eugen,
tanks for feedback. i don´t have a plan about versioning like you do i think but what i meant with undo is reverting back step by ystep like you can do in excel, word or photoshop. if this feature would be implemented with versioning that should be ok. ;)
@ciur commented on GitHub (Oct 11, 2020):
As explained above - will be part of versioning feature. Versioning feature is mentioned as part of #79.
Closing duplicate.