Roadmap and next version announcement #627
Comments
|
Hello @meltyshev, this v2 sounds awesome ! Can you give us any indication of a possible release date? Are you planning an alpha and/or beta so that we can test and contribute too ? Thanks for your work ! |
|
Only thing I can say is it's still some months away. We haven't decided about things like beta stage releases yet. But right now we tend to relase a fully working release version, since the V2 dev version is already being tested on a daily basis and beyond. |
Maybe create beta's branch)? |
|
Unfortunately the publicly accessible boards by link are a must-have for us to switch over from trello. |
|
Public board are on our roadmap but not fully implemented yet. |
|
Thank you for sharing this kind of information It would be awesome to link issues if they exist to this one, so that we can follow any progress and maybe help for some issues |
|
I didn't even notice this post about a v2, sounds interesting. Though I do want to ask about how many people there are in regards to the project that are actively developing? I know this is a passion project and ultimately open source but I'm just curious. :) |
|
In the background this is a team effort of different companies now. Once we go public with the new version it will become quite obvious that this project has gone from passion to purpose for us. Simply stay tuned and thank you so much for all the interest in Planka. |
|
Hi! I noticed that there hasn't been much activity on the repo in the past 6 months, apart from a few translations. I'm curious about why the "v2" isn't public yet—is there something you're keeping under wraps? I want to contribute and improve the project, but if it's being worked on secretly and the same tasks are being duplicated, I'm concerned about potentially working in vain. |
I honestly can't wait to see what has been accomplished, Plankanban is one of the many things I rely on to keep track of what I'm doing etc. Trello is nice and all but it's got a lot of bloat to it. |
|
Okay, it seems like another repo is in process of v2 which is kind of unexpected. I hope the migration from v1 to v2 is smooth enough while my Trello board is going to be read only after 20th May and I need to migration to planka before the deadline. |
|
Hello! I want to say thank you for the product, it is very cool! We moved to it from Trello, but we really miss push notifications and search by boards/tasks Thanks! |
|
Thanks! the best Kanban board around :-) |
That made me chuckle, considering v1 already feels snappier than anything I've tried. Can't wait for v2. One major feature preventing me from switching over (from Vikunja) is seeing tasks/cards from across multiple projects in one view. Is that by any chance something planned or considered for v2? |
|
Isn't this "hidden v2" causing a lot of duplicate work? Why not push it (to a separate branch) so that the community can collaborate on it? |
|
v2 will be released when it's done. We would have no spare time to answer any questions or maintain pull request and a clean codebase and are occupied with managing the current open source version while integrating some of the current community wishes in v2 as well "on the fly" while we speak. v2 is still some time away and will be a full fletched and already battle tested product available to the community. From there on people are welcome to migrate and join development. |
|
@meltyshev, thanks a lot for developing this project and for listening to the users ❤️. |
|
@meltyshev Thanks a ton for developing this project, it helped our team a lot. Do you have an estimate when v2 is expected to be done? |
|
We switched to Planka after Trello went through enshittification. This software is an absolute marvel, even with the current restrictions. We are using it internally for the ScummVM project. Looking forward to the v2. And if you need alpha-testers, we can help. |
Hi! We don't have any estimated date as our resources are very limited and we don't want to promise and then constantly move the date. But we'll be sure to let everyone know as soon as we realise we're getting close. Also, we might consider adding some of the planned features after the release. |
|
Hi @meltyshev I (along with many others!) are now looking for a solution following the 'pivot' of the Jetbrains space product (see here). I am looking for a solution for Agile Software/Product development for small teams (say 1-10 people per product team). I need to be able to represent a hierarchy of product planning items such as this: Epic -> Feature -> Task where Tasks are assigned from a backlog to Sprints for development. I evaluated Planka a while ago and found it to be a fantastic alternative to Trello and looked at using Labels/Boards for this purpose. I have a few suggestions and wonder if these are something you might consider for v2?
|
|
Please can I request user tagging (in descriptions and comments)? When a user is tagged, that user should be subscribed to the card for notifications. Sorry if this is already on the list! |
|
Thanks for your suggestions! Unfortunately we can't do other tasks in parallel as we don't have resources for that and we'd like to finish the basic stuff first as soon as possible and make a release. But after the release we'll definitely think about the next steps and consider your suggestions. We've already been asked about the possibility to create a link between tasks and cards, to turn tasks into cards, we found it very interesting. Also, a lot of people ask about the ability to tag users in descriptions and comments - already in the list of next ideas for implementation. |
|
Hi @meltyshev, do you have any indication on when the v2 will be made public? Considering right now v1 is still in active development by the community, it would be a hassle if we would need to rewrite any new features we add right now for v2. |
Hi! We record all the added changes and will make sure to transfer them to v2 before its release, so it shouldn't be the case that the second version will be missing something from the first version. |
|
Just want to jump in and say you guys have done a great job. We have about 25 people using Planka every day to manage projects and it's now a household name in our company. Really excited for v2 as basically everything you've listed in the roadmap is something that has been brought up in our daily use (for almost 2 years now!). |
|
Hi together, @meltyshev Thank you and your team for all the hard work on planka. In the Roadmap you wrote :"Much improved attachment handling" - does that mean that we can upload more then one attachment at once in the future? I have a costumer, who would like to use planka, for his company too, but they need to upload multiple files in one go. thank you in advanced, and I'm looking forward for the next planka version. best regards Marc |
We're referring to adding other types of attachments, such as links, as well as additional options for viewing content - for example, opening text files directly so that you don't always have to download them. But your suggestion sounds great and it's not that hard to add, so we'll try to implement that. |
That sounds great, I'm looking forward for a new release then. And I use Planka for my company too. |
|
Will there be a way to archive whole projects? |
|
Are we still looking at "months away"? |
We’ve added the option to hide projects, and on the home screen you can toggle the display of hidden projects :) |
|
Would like to pose an API question here, I'm currently maintaining the plankapy Python module (still a work in progress) and was wondering if the new version will maintain the old API endpoints or switch to something else. Will likely branch the project if the API is changing. Also don't know how quickly I'll be able to update it if it is (I'll do my best) so if that's the case it should probably be removed from the docs and resources until I can get it updated. |
|
Hi! Thanks for maintaining plankapy and thanks for the question.
The API will remain the same, with only new endpoints and fields being added. There are a few minor changes to some endpoints, but they are minimal (it's hard to even remember which ones).
Instead of removing the link from the docs, we could simply mention that plankapy for v2 is in progress and there's no need to rush :) |
|
could an enhanced search/chat be implemented as an optional plugin or extension? It would run locally, trained on the json data maybe? Lots of new possibilities, maybe something like https://github.com/instructlab/instructlab or some sort of integration with OpenAI CGPT, Anthropic Claude, Google Gemini, etc.. via a "bring your own API key" set up |
That kinda goes against the whole concept of planka being a lightweight kanban board. No need to shoehorn LLMs into everything. |
|
Just adding my wish list, since I'm also in search of a product to meet my needs.
I feel like my wishes mostly revolve around being able to see all my board details at a glance, without having to repeatedly open each card, or expand tasks. |
Most of these are already in the current release. The description is hidden, but tasks are in the dropdown and tag filters have been implemented for years. As well as due dates. The only thing that isn't available is seeing all that outside the board, but in most of my use cases (don't know about yours) viewing the board is necessary. If you do want to try and get some of this, you can use either the Python or PHP APIs available. Just use those to pull the data you need for a board and send out an email or update a spreadsheet somewhere. Other than that the main usefulness of planka is incredibly fast Kanban for teams. We do 100+ updates to ours and hour and it has never failed. Something that if we didn't have would absolutely kill our productivity. Think of it as a real-time tracker for intent and then implement your other needs on top of that. Having a more verbose API would help, but even the simple one that exists now is good enough for most instances and if you host the database yourself you can just poll it occasionally to gather metrics. |
|
I think either I'm confused, or you misunderstood my point:
Tasks are collapsed, which makes them out of sight. If you know how to autoexpand them, please let me know.. I'd like them to stay always expanded. Also, I don't think you can check them off without opening the card editor. And I was asking about filtering/sorting by priority, not tags. Yes you can use tags for priority, but it becomes hard visually, as the board grows.
How do you see items due this week? I just think it'd be nice to have a view of immediate actions, if your board is too big. Like, out of my entire board, what is due today, and what is due this week, in a list. I'd love to be proven wrong and find out i missed something out of my wish list! I realize I'm not the only user, and maybe I'm asking for things other people don't see useful. |
I think there was a bit of a misunderstanding. I've always treated priorities like tags so didn't get that you meant an entirely separate system for priority.
Having card interactions on the card itself would be interesting, but when you have dozens of users dealing with dozens of cards I can see misclicks from that view causing issue. Maybe reserve that overview for the admin panel?
That's definitely something I've run into when I've had to deal with 20+ tags on a board that has a lot of changing requirements. Having a priority queue would definitely alleviate that (I'm now in agreement with you on having a separate non-arbitrary flagging system lol).
I might be mistaken, but I think one of the recent updates pushed a list sort context option. I don't use due dates that often so I haven't had to filter by them, but if they aren't in that context option that would be a good addition.
This is something Planka doesn't have anything for right now that's for sure, but I've used other tools to get that information. We use Metabase to directly watch the Planka boards and have dashboards that update when the Planka database updates. You can also pull the date field to get timeseries data and do fun BInsryff with that solution. Having it directly in some management panel or overview panel would be nice though.
I did definitely come off a bit aggressively, you can do most of those things in some way currently, but they aren't necessarily as accessible as they would be in other larger systems. |
|
Hello planka team |
|
Any plans for short internal card ids to refer to them in a source code commits? |
Hey! Sorry for the late reply. We're planning to release v2 at the beginning of next year. We've nearly completed all the planned features except public boards, which we can likely add after the release. Additionally, we've also added some other unplanned stuff, so things have been delayed a bit. Please keep in mind that we'll also need some time to migrate all the changes from the current version to the new version.
We don't plan to introduce any new features specifically for v2 at this stage, as that could further delay the release. However, feel free to open a feature request for that :) |
Sorry to steal your time again. But with transitioning from v1 to v2, is this going to be an easy smooth process or is it going to take some tackling? I'm currently running mine from a Raspberry Pi within Docker and I'm honestly not the best when it comes to figuring this stuff out. I'm still learning but is it going to be easy or straight forward to update within this case? |
Of course, we'll try to provide a script for a smooth migration and include relevant information in the docs. However, if we happen to forget, the community will likely come up with plenty of script suggestions, so that shouldn't be an issue. |
|
Depending on export/import functionality, that may be the best move- a one-time manual export from v1 and subsequent import into v2. Either way, super pumped for the release! If you need help testing, let us know! |
|
Dear all, we currently need a public board, and I wonder if there is an estimate of when version 2 will be released. |
|
After reading the conversation above, I have found this statement from @meltyshev in #627 (comment) four comment above yours, in case you missed it:
|
|
@meltyshev small questions as a contributor. The new functions sounds great, and maybe I'm just a bit cynical, but are there any plans for putting features behind a paywall? Overleaf / Sharelatex used to be open source, and now you have to pay up for anything actually interesting. |
I believe they talked about having an optional paid version some where, it's either further up in this post or on another post. |
|
Thanks for the question Jordan! First of all, currently we are thinking about the community and how we can support it as best as we can while at the same time deciding how to deal with the growing number of corporate requests. All we can say right now is that the community version v2 will continue to evolve here on Github and start with exiting new features not seen so far in v1 and that, at the same time, there will definetely be an enterprise version which is also urgently needed to satisfy the needs of our corporate clients. As of now, we have not yet decided about the exact license and configuration of the versions that will be available. Once we've finished with all the legal matters and the few remaining features that still needs to get fully implemented for v2 this is also the moment of release for us. Our major goals for v2 right now are:
|
|
@nickbe, your comment, combined with the unusual secrecy surrounding v2 (e.g., the absence of a public roadmap), does little to easy my concerns. To be specific, I’d be more than willing to implement API keys. However, as it stands, there’s virtually nothing preventing you from taking the feature and making it enterprise-exclusive. You state that “We need to make sure that the community version continues to thrive and prosper.” But how do you plan to achieve this? A thriving and prospering community begins with clear and transparent communication. What will happen to community contributions, and what will your policy be regarding enterprise-only features? |
It wasn't me asking about the corporate stuff, I just remember seeing people talk about it somewhere around here haha. Though I can also see this version being something that the team deploys for those who are wanting this license maybe? |
|
There's nothing unusual here. I simply refused to publish v2 until all new core features are completely implemented, fully tested and operational and the enterprise options are clear. I loath any kind of software that is buggy, unfinished and not battletested. Releasing v2 for me means using being able to fully use its potential. And believe me, we are working our asses off toward the initial v2 release and time is short. But we know from a lifetime of experience that you can pull and pinch a plant as long as you like, but this will not make it grow any faster. Every pull request that we accept for the community version (v1 and all later versions) will automatically become integral part of that community version. At this time we actively working on the details around the enterprise version. Also if you consider the years of work we've put into Planka then I think most people will understand how serious you have to take funding and organisation to do it. Therefore we need to find a good way to do both - a good community version to which everyone can contribute and also how to earn money with it. I cannot answer any details about the enterprise features yet because that would mean discussing things that we ourselves are currently discussing with the team, with interested corporate clients, lawyers and consultants. This as well is "work in progress". Once we've figured out how to do it right, we will communicate as open as possible to everyone. And of course we are more than happy to listen to all your business suggestions. |
and others
Dear community members,
During the last few months, we have seen noticeable users joining the PLANKA community. We feel honored about all this, and our dedication to making PLANKA a complete and battle-tested platform is greater than ever.
For many months, we have already been working on the next generation of PLANKA. The next Open Source version of PLANKA is getting bolder and much more powerful.
It will pack many new features, and below, we have assembled a roadmap of things that are already mostly battle-proof. Others are still being implemented and improved. And some things are left out intentionally because we have yet to decide whether they will make it into v2.
At this moment, several people are dedicating a big part of their lives to this. At the same time, we are trying to maintain and push forward the current version in the best way we can.
Here's a quick Roadmap for the upcoming version:
We want to make sure to deliver something awesome.
Without our community, this would never have been possible.
Thank you all so much for your support 🙏
The text was updated successfully, but these errors were encountered: