Bug 341322 - Cannot decline calendar invitation without filling in reaction field.
Summary: Cannot decline calendar invitation without filling in reaction field.
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail2
Classification: Applications
Component: commands and actions (show other bugs)
Version: 4.14.2
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-11-27 12:28 UTC by Peter G
Modified: 2018-01-31 16:53 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter G 2014-11-27 12:28:05 UTC
When I receive calendar invitations via an employee mailing list, I cannot decline it without filling in the reaction field. Not doing so produces an error message.

Reproducible: Always

Steps to Reproduce:
1. Receive "bulk" calendar invitation, sent to all employees via a mailing list.
2. Press "Decline" at the bottom of the message
3. This brings up a dialog to select identity to respond from
4. Select identity and press 'ok'
5. Leave reaction to invitation empty. 
6. This produces error dialog box saying "You forgot to add proposal. Please add it. Thanks"

Actual Results:  
The problem can be worked around by typing something arbitrary into the response field.

Expected Results:  
It should have declined the calendar invitation, sending an empty response. 

I chose version 4.14.2, when I'm actually running 4.14.3 due to it not being available in the drop-down menu.
Comment 1 Denis Kurz 2017-06-23 20:01:20 UTC
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it.

Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Comment 2 Denis Kurz 2018-01-31 16:53:56 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input.