## File Organisation:
## Item Number : Priority (P0, P1, ...) : Title
## Description (optional)
## <initials> Comment (optional)

## Initials:
## SMI: Stéphane MANKOWSKI
## GDB: Guillaume DE BURE

021:P0:Rework UI on Search & Process
Quite difficult... One thing could be to implement a QTreeView with search
conditions in first level, and associated processes on second level. not sure
that it would solve usability issues, though.
==> Usability issue with this panel has been pointed out by some users on IRC

048:P0: Update documentation

056:P0: Smooth hide/show for editors

060:P1: Forecast based on rate of accounts

086:P1: Export HTML (Table + Graph) using Grantlee template, for printing needs. 

088:P1: Import budget of skg

092:P1:Propriété "execute after import" sur chaque règle de type "process" au lieu d'un setting

097:P1:Export SVG of tables doesn't work

112:P2: Size of account number field for IBAN

115:P1: New advice to detect case inconsistency for comment
select c1.t_comment, c2.t_comment FROM operation c1, operation c2 WHERE c1.id<>c2.id AND  upper(c1.t_comment)=upper(c2.t_comment) AND c1.t_comment<>c2.t_comment;

122:P1: Ability to set a specific date in "account" dashboard widget to have the balance at this date.

123:P1: "Rename" for all dashboard widget

127:P1: Stooq monthly history.txt don't work

128:P1: How to translate x-skg.xml?

133: Replace our graph engine with QCustomPlot or kqtquickcharts

137:P1: In tables, display on 2 lines for better display

140:P1: Deposit guarantee level per bank. Getting a warning when the total over say
different savings accounts at one bank exceeds what is under the government deposit guarantee. Maybe not so 
urgent now, but if at European level it is reduced from €100.000 to
€25.000 again, it would be much more tricky to monitor. This could be
difficult to implement, because it is not per account but per bank. And some accounts, like investment accounts, are not
covered.  

141:P1: Initialize Skrooge with a default document to facilitate testing

105:P1:Study tags on operations ?

145:P1:"Total amount" as a search criterium in Search & Process:

Right now, the "Amount" search criterium in Search & Process works (if I'm
not mistaken) as "if there exists a SINGLE spending satisfying the other
criteria in this rule that goes above this amount, then the rule is met". I
think it could be useful to have a "Total amount" criterium that would work
as "if the sum of ALL the spendings satisfying the other criteria in this
rule goes above this total amount, then the rule is met".


For example, let's say I want to track my spendings in clothing, and I want
to get different alarms when I reach 25€, 50€ and 75€. It would be
useful to include in the 25€ rule the "if Total amount is less than 50€"
criterium, and to the 50€ rule "if Total amount is less than 75€"
criterium, so only one of these rules is going to show up at the same time.

With the current "Amount" criteria, the rule does not work reliabily: Let's
say I add to the 25€ in clothing rule the following criterium; "if Amount
is less than 50€, then the rule is met€". In that case, if I happen to
buy a 60€ trouser, the rule will work as expected (it will NOT show up, as
it will find a greater than 50€ spending in clothing and the criteria will
not be met). But, equivalently, if I but two 30€ shirts, the rule criteria
will still be met as there is no SINGLE spending going above 50€. The rule
firing or not does not depend just on how much I spend, but also on how I
spend it. This is where a "Total amount" criteria would be really useful.
Also I'm sure it would be helpful to make better, more rich rules. 

146:P1: New function to restaure the previous backup

147:P1: Advice if no sub operation has the same date than the operation

Current Sprint
--------------
084:P1: [Space] key to point operations, since space is standard checkbox key?
Not Possible, otherwise every keypress on space (even in the edition panel) would point selected operation 

095:P1:advice in case of "red" budget

114:P1: Better automatic budget based on scheduled operations

135:P1:csv export: http://forum.kde.org/viewtopic.php?f=210&t=112209&p=290153#p290153

144:P1:Inform user when a pointed operation is modified
