Share can't be added, if a share of a different type, but same name exists
Maintainers usually reply within 2 days
Nobody has claimed this yet.
- #2965 by @dartcafe — closed without merging
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- full-stack
Research direction
The issue names no files, tests, or entry points. Reproduce adding the “Users” group when a same-named contact group exists, then trace the share-add path. Done means both share types can coexist under the same name and the regression is covered by a test.
Written by the indexing model from the issue text.
Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github (I've searched it).
- I agree to follow Nextcloud's Code of Conduct.
What went wrong, what did you observe?
Adding a group "Users" to the shares fails if there is already a share with the identifier "Users", but of a different kind (i.e. contact group)
What did you expect, how polls should behave instead?
Adding a group with the same name of another share, but of a different type should be possible.
- Dominant language
- JavaScript
- Stars
- 285
- Forks
- 91
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 52
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nextcloud/polls
-
new
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
nextcloud/polls#4874 · 1 comment ·
Maintainers usually reply within 2 days
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
nextcloud/polls#4978 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
new
Difficulty 3/5 1-2 days Newbie friendliness 52/100
nextcloud/polls#4875 · 2 comments ·
Maintainers usually reply within 2 days
-
UX
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Maintainers usually reply within 2 days
-
UX
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 2 days
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
andromarces/agent-loops#886 ·
Maintainers usually reply within 1 day
-
bug effort:low model:light plan planner:gpt-6-1-sol tests
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
B: visual
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
FreeTubeApp/FreeTube#9929 ·
Maintainers usually reply within 1 day
-
🐛 Bug: `--clear-screen` not very useful (at least not for dealing with large test/error output)Openstatus: in triage type: bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mochajs/mocha#6428 · 1 comment ·
Maintainers usually reply within 1 day
-
🔧 in development
Difficulty 2/5 1-3 hours Newbie friendliness 72/100