mirror of
https://github.com/ciur/papermerge.git
synced 2026-04-25 12:05:58 +03:00
[GH-ISSUE #208] Q: Tag usable by only one user? A: Tags are per user #170
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#170
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 @ciur on GitHub (Nov 14, 2020).
Original GitHub issue: https://github.com/ciur/papermerge/issues/208
Originally assigned to: @ciur on GitHub.
Bug reported on r/papermerge
Description
I created a tag (2020) as the admin user (user A), but then tried to use it under a different login (user B). I found I could not use/create that tag, but got no warnings or other information, or perhaps it was just invisible?. Anyway I saw no evidence of the tag in the user interface. I tried to rename another tag (2020a) to that name (2020), but was told that tag already existed. So, I went into the database and reassigned the 2020 tag to user B, and then I could use it as user B.
Expected
Tags are per user, this means when user B renamed tag 2020a to 2020 there shouldn't have been an error.
Correct is user A to have his own tag "2020" and user B his own tag "2020".
Actual
User B was told from creating tag "2020"
Info: