Hi, and sorry again if this should be a Feature Request.
One of the things I’m hoping for in Fibery with all its flexibility is the ability to give the user the chance to come up with a custom archiving strategy.
I’ve met with quite a few ways this is handled in other apps:
Manual archiving: Wrike for example does not archive anything automatically. You have to create an “archive” area, and tag every archive task with this folder. “Done” tasks are removed from a lot of default views as they are not considered “active,” but this is a very limited solution, requiring way too much manual work.
Auto-archiving after a certain amount of time. Jira will remove issues out of a “done” column after a certain amount of time, into the archive. This is not a bad solution, as they are still visible in search results. But customizing this is a bear in Jira. I tested another app, Favro, that simply let you pick how many days a “done” item stayed in that column in one simple drop down.
Generally I would like to be able to archive certain entities, like the ones I use for tasks/issues such as in the apps I talked about above, but other entities I do not want to have archive at all, such as features of my website. I am not clearly seeing any evidence of archiving at all right now in Fibery. If this is intended, could you let me know if with the release of Automations there will be some good ability to, in essence, create a custom archive solution such as what I’m talking about here? Summing up, certain rules for certain entities so they’d effectively “disappear” from view into an archive, while other entities would not archive at all?
Thanks as always for the help with this!