Scheduled card creation/replication

https://github.com/wekan/wekan/wiki/New-card-with-Python3-and-REST-API

@xet7 I need some help in understanding the roadmap/milestones of the project.

I could not figure out the order (timeline) of planned features in https://boards.wekan.team/b/D2SzJKZDS4Z48yeQH/wekan-open-source-kanban-board-with-mit-license

What is the meaning (in terms of development timeline) of the lists "Trello has it", "Jira has it"?

What is the meaning of the ordered lists "1. In Progress", "2. TODO...", "3. TODO..." etc. Is there any precedence? Why "#. TODO Paid..." are in different lists instead of one unique ordered list? Does this mean they are different paid requests from different "sponsors" and that there is an implicit delivery order?

Also, how should I understand the timeline of https://github.com/wekan/wekan/milestones ?

Or even for specific "themes" such as https://github.com/wekan/wekan/milestone/54

I would appreciate any help in understanding the roadmap/planning/milestones of the project in order to have a clearer view of what to expect for the following months. It will help me present/defend the project in my company and also understand how can I help (as a independent contributor) to the project.

Thanks in advance for your help.

At this Roadmap https://boards.wekan.team/b/D2SzJKZDS4Z48yeQH/wekan-open-source-kanban-board-with-mit-license those that have some amount of money number, those have already been fully or partly prepaid. I have promised to implement all paid features, even those that could have small amount of money like 10 euro for some big feature, although those most likely will be last to be implemented, and it would be really nice if someone could contribute to those more. I try implement those with highest amount of money first. Those that do not have any number are waiting for funding.

As a contributor, you should implement those first that are most important to you, and send pull request.

Pull requests are usually checked and added to official release fast.

My priorities are: 1) Security fixes 2) Paid features 3) Others

Correction: 2) Paid features and fixes

At Roadmap those C1, C2 etc are customer numbers in time those where added

Already done features and fixes are removed (or archived) from Roadmap

Thank you very much for your explanation! One last question: how should I interpret the items that are in the Milestones ( https://github.com/wekan/wekan/milestones ) but not in the Roadmap (https://boards.wekan.team/b/D2SzJKZDS4Z48yeQH/wekan-open-source-kanban-board-with-mit-license) ?

Milestones are kind of grouping of issues, but not all issues have been added to Milestones. Wekan Roadmap originally at 2016 at Wekan kanban board, then it was moved to wiki and milestones, and after that to Wekan kanban board. For any open issue, someone should check does that bug exist, or is that feature already implemented, because not everything in issues is up-to-date, there is about 600 issues and there can be duplicates etc.

All Wekan changes are listed at ChangeLog https://github.com/wekan/wekan/blob/master/CHANGELOG.md , there someone can search if some feature or fix has been added or removed. Or try to find that in Wekan, does something work. Sometimes some menu options have been moved to different menu that is more logical place for it.

Recently I have also added new wiki pages for new major Wekan features to wiki https://github.com/wekan/wekan/wiki , there at right menu Features topic

There has been about 180 contributors to Wekan, and Wekan has many features that I have not yet used, because I have not had time to test how they work.

There are also Wekan related repos at https://github.com/wekan , like for logging etc, from Wekan contributors

About features, I did recently add changing custom logo at Admin Panel / Settings / Layout, for login logo and top left corner logo

Currently I'm working on fixing CSV Import/Export and bug about only 20 recent comments on card

I try to implement Search in All Board this year

and maybe also Teams/Organizations

I am doing a little tests about changing database, but nobody has paid for that, so it remains to be seen do I get it sometime working.

Like changing from MongoDB to some other database

Anyway, if that happens sometime, Snap will get automatic migration for it

Thank you one more time for the information and for your time. I've been closely following your work for 3 weeks and you are certainly doing a great job! Congratulations!!!

I have just started to run a trial of Wekan as a Trello alternative with near 150 users that actually do use Trello (daily). From the feedbacks I have received so far, they are really enjoying Wekan and they are only really missing Trello's Scheduled card creation/replication power-up (https://trello.com/power-ups/57b47fb862d25a30298459b1/card-repeater), that according to them, is a major productivity feature that advocates towards they keep using Trello.

I believe (and hope) that implementing this feature (card-repeater) can be done without big efforts by using the already deployed rules feature (as sketched here: https://github.com/wekan/wekan/issues/2476).

I am really hoping someone can work in this issue in the very near future.

One more time, thank you very much for your time and for all the answers provided.