Bug 321083

Summary:	version 4.8.5 does not allow scheduled transactions on a bi-weekly (or fortnightly) basis.
Product:	[Applications] kmymoney	Reporter:	Pete <pierre.casey>
Component:	general	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED NOT A BUG
Severity:	normal	CC:	ostroffjh
Priority:	NOR
Version:	4.6.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description Pete 2013-06-13 02:25:33 UTC

Common payroll practice in USA is 26 pay periods in a calendar year, once every two weeks.  Can not enter a scheduled transaction on this basis.  Only options for schedule frequency are one, day, week, half month, month, year.  Really need a bi-weekly or fortnight option.

Reproducible: Always

Steps to Reproduce:
1.click on scheduled transactions
2.click on new
3.click on frequency.  No option for bi-weekly or fortnight
Actual Results:  
cannot schedule paycheck deposit.  need to enter it each time.

Expected Results:  
expected an option for 1 time every two weeks, or bi weekly, or fortnight.  no such option

Comment 1 Jack 2013-06-13 02:33:13 UTC

Can't you choose "week" in the dropdown, and 2 in the frequency box?  That's every 2 weeks, not 2 times a week, in case it's not obvious. Separate question - do you think there is a change from previous versions in how this is handled?

Comment 2 Pete 2013-06-13 02:37:23 UTC

Choosing 2 and week would logically result in twice a week entries.  I'll try it and see if it does in deed result in every 2 weeks.

Comment 3 Pete 2013-06-13 02:41:49 UTC

Ok I tried entering 2 and week.  it lists the frequency as "Every Other Week", so what we have is just the ubiquitous "failure to communicate," not a real bug.

Comment 4 allan 2013-06-13 08:22:26 UTC

On Thu, 13 Jun 2013 02:41:49 +0000
Pete <pierre.casey@yahoo.com> wrote:

> https://bugs.kde.org/show_bug.cgi?id=321083
> 
> --- Comment #3 from Pete <pierre.casey@yahoo.com> ---
> Ok I tried entering 2 and week.  it lists the frequency as "Every
> Other Week", so what we have is just the ubiquitous "failure to
> communicate," not a real bug.
> 

Perhaps you could close the bug then?

Allan

Comment 5 Pete 2013-06-13 14:38:38 UTC

Sorry, I am new at this, did not realized I could close the report.  I will mark it resolved, and invalid, because the issue is resolved, and was not a programming issue, but one of English language semantics.   Thanks to all for assistance.