Bug 303562

Summary:	Order of columns in ledger view is not adjustable.
Product:	[Applications] kmymoney	Reporter:	lenka.vasenkova
Component:	ux-ui	Assignee:	KMyMoney Devel Mailing List <kmymoney-devel>
Status:	RESOLVED FIXED
Severity:	wishlist	CC:	jvapr27
Priority:	NOR
Version:	git (master)
Target Milestone:	---
Platform:	Microsoft Windows
OS:	Microsoft Windows
Latest Commit:		Version Fixed In:	5.2

Description lenka.vasenkova 2012-07-15 14:43:00 UTC

It would be great to have position of the ledger columns adjustable. Especially deposit (debit) and payment (credit) columns are those which confuses me. In our country it is usual to have a debit on the left side of a transaction and a credit on the right side of a transaction. 

Reproducible: Always

Comment 1 Jack 2023-02-06 01:07:32 UTC

Adjusting some headers, as this is still relevant.  In master, right clicking on a header lets you select display of optional columns, and left clicking lets you adjust the sort order.  Column width can be adjusted, but not column display order.

Comment 2 jesse 2023-02-06 01:34:27 UTC

Thanks for keeping it open! 

Much appreciated! I look forward to the implementation if possible. Great work on this software btw.

Comment 3 Thomas Baumgart 2023-02-06 07:02:10 UTC

(In reply to Jack from comment #1)
> Column width can be adjusted, but not column display order.

That is not true: drag and drop of the column header lets you change the order of the columns. See https://invent.kde.org/office/kmymoney/-/commit/0a9cb4f01e0867dcc67311098bae75b5f3948f5d and bug #445510. I leave it in waitingforinfo for you to confirm and close as fixed.

Comment 4 Jack 2023-02-06 21:51:10 UTC

Not sure why it didn't seem to work yesterday.  Drag and drop of column headers does work in master.  Closing as fixed.

Comment 5 jesse 2023-02-11 18:58:34 UTC

Thanks all! 

Do we know when this version will release? How long does it historically

Comment 6 Jack 2023-02-11 19:10:39 UTC

If it were going to be in 5.1.4, for example, we could make a reasonable guess between weeks and months.  Unfortunately, master branch contains enough changes, and is still a work in progress, that there is no specific timeline for release.   We are using 5.2 as a placeholder so we can fill that field for several bugs, to make it clear the work has been done, but will not likely be released in any 5.1.x version.