nextcloud / nextcloud/deck

Deck calendar integration visibility cannot be toggled for board sharees

Open
#2,661 3 comments 14 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

1. to develop bug feature: sharing integration: tasks / calendar
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Describe the bug
As a Deck board sharee, I cannot hide calendars. Invoking the usual action ends up with an error (see below).

To Reproduce
Steps to reproduce the behavior:

  1. User Alice shares Board Foo with user Bob.
  2. User Alice creates some cards with due dates.
  3. Alice opens their calendar and sees a list of their calendars, among which there is one called "Deck: Foo". The above set due dates appear in the calendar view as events.
  4. Alice clicks on the calendar list entry "Deck: Foo".
  5. The entries for "Deck: Foo" are not visible any more, the list entry is greyed out.
  6. Bob opens their calendar and sees a list of their calendars, among which there is one called "Deck: Foo". The above set due dates appear in the calendar view as events.
  7. Bob clicks on the calendar list entry "Deck: Foo".

Expected behavior
The entries for "Deck: Foo" are not visible any more, the list entry is greyed out.

Actual behavior
The entries for "Deck: Foo" are still visible. The list entry is not greyed out.
An error message appears: An error occured, unable to change visibility of the calendar.

Screenshots
image

Deck 1.2.2
Calendar 2.1.2
Nextcloud 20.0.4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue using the listed Deck, Calendar, and Nextcloud versions, following the Alice and Bob sharee steps. Trace the calendar visibility action for a board sharee from the calendar list through the error response. Done means Bob can hide and show the “Deck: Foo” calendar, with the entries and greyed-out state updating without an error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
full-stack
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.