Bug 398981 - Wrong filter executed when doing "Jetzt anwenden" / "Apply Now" in the Filter Dialog
Summary: Wrong filter executed when doing "Jetzt anwenden" / "Apply Now" in the Filter...
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 5.9.1
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-23 09:34 UTC by JDiel
Modified: 2023-01-01 05:20 UTC (History)
1 user (show)

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 JDiel 2018-09-23 09:34:26 UTC
SUMMARY


STEPS TO REPRODUCE
1. Enable "Filterprotokoll anzeigen" / "Filtering log"
2. Mark one of your filters (not the first one)
3. "Jetzt anwenden" / "Apply Now"
4. Review "Filterprotokoll" / "Filtering log"

EXPECTED RESULT
The selected filter should be applied

ACTUAL RESULT
a different filter was applied than the one I've choosen

SOFTWARE VERSIONS
(available in About System)
KDE Plasma Version: 
KDE Frameworks 5.49.0
Qt 5.11.1 (kompiliert gegen 5.11.1)
ADDITIONAL INFORMATION

When exporting filter rules, the order of rules is different from the order displayed in the filter dialog, namely alphabetically by numbers:
[Filter #19]
...
[Filter #2]
...
[Filter #20]

This is counterintuitive and maybe is related to the error reported here.
By the way, is there a documentation about the format and syntax of filtering rules? I've started writing a Python script to create a text file, which can be imported in the filtering dialogue.
Comment 1 Laurent Montel 2018-10-30 06:52:43 UTC
it's not the problem but indeed kconfig save as alphabetical order.
I search how to fix it.
Comment 2 Justin Zobel 2022-12-02 01:23:00 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 3 Bug Janitor Service 2022-12-17 05:13:49 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2023-01-01 05:20:25 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!