Optional archiving

[1451678]

I would like to have a setting option or something like that so that my entries are not archived after adding time entries to redmine, but remain in the file with the time entries. Since I book daily, the old entries disappear too quickly in the archive for me.

[BuJo]

I haven't really touched the archive feature at all from what it was.
I think the initial Users work by adding to the timesheet for a week and transferring that once a week to the redmine instances.

I haven't understood what I actually want, but my usual mode is to have a single timesheet file per month and manually putting them with a postfix of -<year>-<month>.B beside the original file.

So I would love some more design happening around the archive feature before implementing anything.

[dgrammlich]

I also book daily with the TUI based Buchungsstreber. It has no automatic archive function, therefore I move the buchungen.yml file to the archive folder at the end of a month and rename it to <year>-<month>.yaml. As I forget it often they sometimes include two or more month. 😅

I mostly do not need the previous days or month to copy entries because my reoccuring entries are automized and the new ones I often have as browser tab nearby, so I can get the issue number or any other information from there if needed. Or I make templates for them, too.

With my workflow I do not really have a need to archive, mostly I move forward in time and have no need to look in the past. In the few cases I need to it is almost more comfortable for me to look in the booked times of the issue in the browser. So I actually don't know why I archive, some "better safe than sorry" or "don't throw away" issue or something. 😄