Issue 8884

draft moves changing journal with different sequence does not change move number
Nosy list
ced, reviewbot, risto3, roundup-bot
Assigned to

Created on 2019-12-01.14:07:54 by risto3, last changed 1 month ago by roundup-bot.


New changeset 59f6312ad5a3 by Cédric Krier in branch 'default':
Make move's journal read-only once numbered
New changeset 036fed0cfc20 by Cédric Krier in branch 'default':
Make move's journal read-only once numbered
Author: [hidden] (risto3)
Date: 2020-12-10.16:48:14

This does now mean that if the journal is wrong the whole draft move needs to be deleted and recreated from scratch.
(neither copy/paste nor drag/drop seem to work in GTK client).. also duplication is invariably to the same journal.

It would be nice to have ^ (above) in order not to waste time re-entering what may be a number of move lines where export/edit/import via the accounting moves form is rather intimidating for the average user.

Perhaps an alternative would be to prompt the user to confirm changing the journal, then do the create new move for him retargeting the move lines which, given the context, is rather trivial.

Author: [hidden] (risto3)
Date: 2019-12-01.14:07:53
journals have sequences that may be different, and frequently use a prefix and/or suffix to indicate the journal.

if I create initially a move in one journal (say OD) but change it because it needs to be in another (like EXT), the move number is not corrected to use the sequence of this last journal.

This is a rather large source of confusion given even the GL reports this number .
Date User Action Args
2020-12-17 22:22:07roundup-botsetmessages: + msg63333
2020-12-17 22:22:03roundup-botsetmessages: + msg63332
nosy: + roundup-bot
status: testing -> resolved
2020-12-10 16:48:14risto3setmessages: + msg62542
2020-12-10 12:28:38reviewbotsetmessages: + msg62539
nosy: + reviewbot
2020-12-10 12:12:03cedsetkeyword: + review
reviews: 345181002
status: in-progress -> testing
2020-12-10 11:59:47cedsetassignedto: ced
component: + account
nosy: + ced
priority: wish -> bug
status: unread -> in-progress
type: behavior
2019-12-01 20:51:29cedsetpriority: bug -> wish
2019-12-01 14:07:54risto3create

Showing 10 items. Show all history (warning: this could be VERY long)