nextcloud / nextcloud/calendar
Feature request: Add link from birthday calendar events to corresponding contact
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
[!TIP]
Help move this idea forward
- Use the 👍 reaction to show support for this feature.
- Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
- Subscribe to receive notifications about status changes and new comments.
Is your feature request related to a problem? Please describe.
When using the Contacts Birthdays calendar, the birthday events are read‑only and can only be changed by editing the corresponding contact in the Contacts app. If I notice an incorrect birthday while viewing the calendar, I first have to manually search for that contact in the Contacts app, which is inconvenient.
Describe the solution you'd like
I would like to request a feature that adds a direct link or button in the birthday event popover (or detail view) to open the corresponding contact. For example, an “Open contact” link that uses the contact’s ID or vCard UID.
This would make it much faster and more intuitive to correct or update birthdays and would improve the integration between Contacts and Calendar.
Describe alternatives you've considered
none
Additional context
none
Contributor 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.
Research direction
Start at the Contacts Birthdays calendar event popover or detail view and trace how the corresponding contact ID or vCard UID is available. Check the existing Calendar and Contacts integration, then add an “Open contact” link that opens the matching contact; done means birthday events provide a working link while remaining read-only.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100