nextcloud / nextcloud/calendar

Quick create action / centralize create actions location

Open
#7,535 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. to triage design: brainstorming 🧠 enhancement Feature: Appointments Feature: Scheduling Feature: Talk
Dominant language
JavaScript
Stars
1.2k
Forks
332
Avg merge
16h 13m
Merged PRs (30d)
137

Description

Is your feature request related to a problem? Please describe.

As a user I might need create different event quickly one after the other, like create a simple event, create a meeting, then create a proposal. It would be nice to centralize the creating process to a single location on the interface.

Describe the solution you'd like

It would be nice to have a split button where the current "+ Event" is to:

  • Create meeting (Calendar event with talk room already preset)
  • Create proposal
  • Create calendar
  • Etc
Describe alternatives you've considered
  • Searching the interface for the + sign next to all the section headings
  • And remembering to add a talk room
Additional context

No response

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

Start by tracing the current "+ Event" action and the "+" actions beside section headings in the interface. Determine how meeting, proposal, and calendar creation currently begin, then define the centralized split-button behavior and verify that each requested creation path remains available.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.