-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add contact groups as attendees for an event [$50] #167
Comments
Maybe linked to #163 |
I'm actually not sure if we can query for contact groups via the contacts php api. Also, how to show if some users of a group have no e-mail address |
Just don't show them. :-) |
I'd offer the following: |
Should groups expand to members / contacts and add the "person" to the event or just added as group of persons? Expand the groups to users / contacts / persons would be flexible (add / remove single persons from event). |
This would be my choice for a first implementation. That should be fairly easy and doesn't require modifications to the Nextcloud server itself. |
Added 50 € on Bountysource for this indespensible calendar feature. But for the sake of privacy there should be an option to hide the list of invitees! Thanks for the calendar app. |
Any updates about implementing this feature as temporary solution ? |
Nope, as always: This is a free-software project. Pull-requests are very much appreciated. |
Where can I find the relevant code part ? |
To implement this, you would have to alter the ContactsController: We have an InviteesListSearch component. In the search method ( |
My PHP knowledge is too basic for that and never worked with vue before. |
What do you think about adding the talk room participants as attendees? |
This discussion and the related issues that have been closed for being duplicates takes some wild directions in my opinion. Some are talking about contact groups (from the Contacts app), some are talking about User groups (from the user management / LDAP). Even Talk rooms have been brought up. tl;dr: We have the request to share with
If you, @tcitworld (as issue initiator) agree with me, would you mind changing the issue title? |
Looks like bountysource is no longer the default. @tcitworld do you plan to develop this feature? |
Hello, any news ? This feature is absoluelty essential and is a basic for every groupware. How can we help ? What is actually blocking this feature ? |
This is what people want to use... People are simply trying to replicate MS Exchange Distribution Lists functionality here (used for decades). That is: System Account users > groups of users > email/calendar Every big enterprise with MS Exchange has some kind of lists set up that email/calendaring can access so they can email communications to _DL_ALL_INTERNAL_EMPLOYEEES and _DL_ALL_EXTERNAL_CONTRACTORS Nobody wants to have to onesie twosie manually add recips, especially when you're emailing "all". The nextcloud calendar app already ignores atendee results where the nextcloud user does not have an email field populated, right? So we're at least able to get a list of users and see their email field. Ok, that's a start. Why not just do something like: Option 1:
Keep it simple. Admins will know what to do from there (add an email address for the user, or remove the user from the group) Option 2:
Option 3: |
That's a good idea. I'd also include a notification for the user so they know it was added. But that's all extra code. If I were the app author/maintainer, I'd just "no soup for you" if someone in the group doesn't have an email address for version 1 of this. "Email adress for group member $username is missing. Stopping." |
Btw, if anyone is interested in DIY instant bounties but you don't know how to code, you can always post the project for a fixed price at some place like Upwork, and make sending a pull request to the maintainer (in addition to sending the patch & instructions to you immediately) as part of the deliverable. |
The participant event module should suggest contacts groups from the contacts app.
Related issues
The text was updated successfully, but these errors were encountered: