I use gmail via IMAP. I want to mark messages automatically, so I created tag, than I created filter with action "Add tag". On closing window "Select tag" (Filter tag is missing) appears. I also use groupware (owncloud), so my tag list also contains tags from owncloud calendar.
could you paste screenshot about your problem ?
I didn't understand what do you do to show bug.
You want to create filter so you will create tag where ?
Created attachment 82860 [details]
1. Just marked message with new tag
I just created new tag via message context menu -> Mark message -> Add new tag. Here comes another bug (should I create separate report?) — tons of duplicated tag "pyqt list".
Created attachment 82861 [details]
2. Added filter
I created new filter with 1 action. As you can see I have no choices: all other tags (pc, health, ... from to-do lists created in Owncloud Groupware calender) disappeared.
Created attachment 82862 [details]
3. Pressed Apply button in Filter Rules dialog
I pressed Apply button in Filter Rules dialog and got this window. As you can see "pyqt list" remained in Filter Actions.
Same here with 4.11.3 on debian unstable.
The label specified in the action part of the filter is forgotten: when I edit the filter again, an action "tag" is still selected, but the selected tag is "task list" (first of the drop down).
Also, I tried exporting the filters, this is what they look like:
ToolbarName=<List-Id>: <<mangled list name>>
contentsA=<<mangled list name>>
name=<List-Id>: <<mangled list name>>
We can see that arg0 is empty here.
When I reimport this filter with the arg0 filled in, kmail2 asks me for the correct label because it can't match it and forgets it nonetheless when I click "apply".
Confirm this bug. KMail 4.12.2
Happens also with Ubuntu 12.04, with Kmail2 from PPA.
*** Bug 326068 has been marked as a duplicate of this bug. ***
Confirmed in Opensuse 13.1 KMail 4.11.5. I would love to help find this if I knew where to look.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?
If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.
*** This bug has been confirmed by popular vote. ***