mirror of
https://github.com/plankanban/planka.git
synced 2026-02-25 03:14:50 +03:00
Version 2 has been released! #695
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nickbe on GitHub (May 10, 2025).
The long-awaited new PLANKA version 2 has finally been released! We deeply appreciate everyone's patience, support, and contributions throughout this journey. Your dedication and enthusiasm is the heart and soul of this community.
Enjoy the latest updates, and let's continue building great things together! 🚀
— Your PLANKA Team
@Lka1988 commented on GitHub (May 10, 2025):
Very cool, thank you!
I do want to note, for the less-experienced of us (cough me cough) - the Docker upgrade instructions are a bit confusing. I had to keep my containers running or the backup commands wouldn't work, and I had to manually stop the containers after the "db:upgrade" part. Not huge issues, something that someone more experienced would probably understand better, but still, just wanted to point it out.
Great release, otherwise. I dig it. The sorting options are really helpful haha.
@nicedevil007 commented on GitHub (May 10, 2025):
Hi all, I run through the processs for upgrading:
Should we post the issues facing the upgrade process here or in seperate issues?
I faced the issue with the db upgrade part, tested it with 2 instances, one was done as root and one with the planka user in our ubuntu servers (all manual installations).
I'm always facing this issue here:
@meltyshev commented on GitHub (May 10, 2025):
Thanks for reporting this! We'll definitely look into it and re-test each step.
@meltyshev commented on GitHub (May 10, 2025):
Thanks for reporting this! You're right - I just tried it myself and encountered the same error. Already in the process of updating the docs...
Here it's totally fine, will be easier to handle :)
@meltyshev commented on GitHub (May 10, 2025):
The docs have been updated. Tested everything again and didn’t encounter the same issues.
@FibreFoX commented on GitHub (May 10, 2025):
First of all: thank you for (finally) sharing the new version. It really took a long time, but it finally is here, and I am thankful for that 😺
I have a question: is there a reason, that comments are now "right-aligned"?
Coming from other ticket-systems it is a bit confusing so see it there, v1 had if oriented to the left, and it felt better that way, because reading from left-to-right with mixed length comments it gets confusing for the eye.
On the topic of UX, maybe you want to add a tiny label for "board actions" too, because when "in trash view" the button changes the icon, and I got lost searching for the previous "board"-icon
One question regarding the new version: should we report that kind of stuff here in this issue ticket, or should we open a new one? (Do not want to pollute here)
@hazzuk commented on GitHub (May 10, 2025):
First off, thank you for your hard work and dedication to Planka. Out of all the Docker containers I've selfhosted over the years, I feel Planka is most likely my favourite. It's been a joy to use the last six months.
Migrating to v2 was also a breeze and all the new improvements are going to be very useful. Testing the new version and reviewing the changelog I thought I might note down some general feedback:
v2 Features Feedback
The term 'Project' for card types is confusing, as it's the same term used with creating 'Project' boards ('task' would be preferable)
The editor UI for 'project' and 'story' card types have no easily discernible differences (only the top left icon and a few less right hand options on stories)
The 'Board', 'Archive' and 'Trash' views have no easily discernible differences (only the top right icon)
The selected list colour doesn't display on it's cards (could either effect the card backgrounds, or maybe a dot/outline/card title highlight etc)
'Archived' cards don't look "Archived" (aka old/aged)
Can't convert a 'Shared' (existing v1) project to a 'Private' project
Can't sort or manually reorder cards on the 'Grid' view (with grids and stories in v2, you're about 99% of the way to replacing Google Keep for me)
There is no large visual warning the user is in edit mode (something like a 2px coloured line spanning across the top of the app)
Additional Feedback
Ability to save global label/custom fields/task lists/board columns presets
Mention users with @{username}
GitHub integration (for now 'Link attachments (attach URLs)' is a great help in this regard)
Create documentation in Projects. This last one is maybe a large ask (and one that might dilute the singular 'kanban' focus of the app). But having used the amazing new markdown editor, and seeing how notes are kind of supported with the use of stories. I'd love a way to create 'pages' (think a far simpler version of something like BookStack).
Once again, thank you and awesome work <3
(this was written using the new markdown editor, worked great)
@nickbe commented on GitHub (May 10, 2025):
Thank you for the extensive feedback already on the first day. Indeed several things are on our own lists and not everything is already perfect. And I think that lots of suggestions are indeed helpful and we will discuss them. Again thanks 😊 for taking the time to review V2 so fast.
Cheers
@nickbe commented on GitHub (May 10, 2025):
Some short comments to this:
Indeed they are. When working in a team and with comments on both sides we decided that a modern conversation style would be better. Like this:
You are right. It simply seemed easiest this way. But the UI is not optimized in many places and we will think about how to enhance it.
Later having a fresh issue ticket will be better because discussions will be easier.
But right now - seeing that you guys already dig into v2 like this is enjoyable enough for me and it's fine😄
@nickbe commented on GitHub (May 10, 2025):
First, thanks for the feedback. We are happy to have it.
We didn't like "Task" and project seemed obvious enough. But I'm happy to try and find something else entirely. If successful we rename it.
This is still work in progress. The difference will be much more obvious in due time.
You're right and I feel the same way. We will optimize the UI further and surely find a better way to indicate the current location.
This on is tricky. For me "colored" cards are a visual nightmare, so the little colored indicator was chosen because we didn't want too much color at all. Let us think about this. Maybe some additional option per user could solve the problem.
Good point. It also falls under the category "work in progress". We simply didn't find the time to really design something better.
It's on our list for later. But I feel the same.
Yeah we like the new editor too. It solved so many issues at once 😁
We plan something like that already
@meltyshev commented on GitHub (May 10, 2025):
This can be done by clicking on a manager and then selecting "Assign as owner" (the manager must be the last one remaining). To make this clearer, it might be better to display the button under the "Danger Zone" section (same as "Make Project Shared"). We can even always show the button and simply disable it when there are multiple managers, with a message explaining that you need to be the last manager in order to convert to private.
Btw, big thanks for all the feedback!
@nicedevil007 commented on GitHub (May 10, 2025):
tried it again and made sure it is on 1.26.2 version prior to update.
on little thing missing in the docs now:
after switching to the planka user with
sudo -i -u plankawe should change the directory to/var/www/plankaagain otherwise npm will fail ofc ;)@meltyshev commented on GitHub (May 10, 2025):
Oops 🙈 Thanks for mentioning that!
@JamesMowery commented on GitHub (May 11, 2025):
Is there a way/option to have a Task List always added to new cards that I'm not seeing? I use the feature so often that having to click to add a task list every time is an annoyance and regression from the prior version. Beyond that, enjoying it so far!
@akinin commented on GitHub (May 12, 2025):
A magnificent and long-awaited update! Sincere thanks to the developers!
I'd like to share important information for those upgrading Planka when installed through Portainer.
When executing the migration commands described in the official instructions, you must use the following format:
docker compose -p planka run --rm planka cp -av /app/public/project-background-images/. /app/public/background-imagesdocker compose -p planka run --rm planka npm run db:upgradeWhere the
-p plankaflag specifies the project name. This is critically important because without this parameter, commands executed in the directory/var/lib/docker/volumes/portainer_data/_data/compose/4(your number may differ) will create volumes with a numeric prefix (e.g.,4_db-datainstead ofplanka_db-data), resulting in a mismatch with your existing data volumes.@toras9000 commented on GitHub (May 12, 2025):
Thanks to Planka for the update.
I have been using v1.25.0 and have updated to v2.0.0-rc.2 to try it out.
OIDC is used for user management.
I followed the upgrade guide and was able to upgrade successfully.
One point, it would be helpful if an alternative to
ALLOW_ALL_TO_CREATE_PROJECTSbeing discontinued is mentioned in the guide.I got a little lost trying to find
OIDC_IGNORE_ROLES.The one thing I felt was missing when I touched v2.0.0 was the specification of the default role of the user.
Users who have been using
ALLOW_ALL_TO_CREATE_PROJECTSwill probably want to makeProject Ownerthe default.In my case, it was.
... I rely on translation tools. I'm sorry if there is a strange sentence.
@meltyshev commented on GitHub (May 12, 2025):
Thank you 🎉 and thanks for this information! Definitely should be added to the docs :)
@meltyshev commented on GitHub (May 12, 2025):
HI! That's a good point, it seems we should add default parameters to be used when creating a user.
@filcuk commented on GitHub (May 14, 2025):
No issues upgrading on docker.
I have a bit of an odd setup with various sets of compose files, so it was easier to just add the upgrade command to compose directly, just as a tip for others in a similar situation:
Is it not inadvisable to use
POSTGRES_HOST_AUTH_METHOD=trust? The docker compose template provided in docs uses this, which I suspect leads to many people not knowing or bothering to change it.Custom fields, archival, card types, views, project screen - fantastic improvements, worth the wait. Thanks for the amazing work.
@stufently commented on GitHub (May 15, 2025):
where apprise in helm chart ?
@pixolin commented on GitHub (May 18, 2025):
Hi everyone.
I've been using Plankanban since the end of December to plan a trip that my wife and I start in a week. The software has already been very helpful in collecting a lot of information, planning flights, train journeys and hotels and storing tickets and reservations etc.
The only thing I personally missed so far was a calendar, but as a workaround I simply created a workspace “Calendar” with cards for each day of the trip, which does the job.
A week ago I installed the new Docker image for release 2.0-rc2. Update went without any issues and everything continues to run smoothly and without errors. Cool. Many thanks to everyone involved for this great software.
But one question remains: a week before we set off on our trip, I wanted to check whether there are any further updates. This issue here now claims that version 2.0 already had been released. However, the list of releases only shows a release candidate 2 as a Docker image.
As I understand it, a release candidate is a preliminary version for testing before the actual release? Is there still another image coming, which contains the final release? Or have I overseen a Docker image?
@keksie commented on GitHub (May 18, 2025):
When a user does not have the global manager role, they cant be added as a manager to a project. This is a nuissance, as they can be granted the role, then added as project manager and revoked the role. However, to remove them as manager again they need the global role.
Also, I do not want them to be able to create new projects, so leaving them the role assigned is not viable.
Bug/Feature?
@Brainopps commented on GitHub (May 18, 2025):
Just installed V2 and it updated beautifully. The update added everything that I had hoped for. I appreciate everyone that has worked on this project! Thank you!
@jaimedmp commented on GitHub (May 19, 2025):
Hi,
I am facing an issue upgrading the planka. Below is the details
planka-1 | Error: The migration directory is corrupt, the following files are missing: 20180721020022_create_next_id_function.js, 20180721021044_create_archive_table.js, 20180721220409_create_user_account_table.js, 20180721233450_create_project_table.js, 20180721234154_create_project_manager_table.js, 20180722000627_create_board_table.js, 20180722001747_create_board_membership_table.js, 20180722003437_create_label_table.js, 20180722003502_create_list_table.js, 20180722003614_create_card_table.js, 20180722005122_create_card_subscription_table.js, 20180722005359_create_card_membership_table.js, 20180722005928_create_card_label_table.js, 20180722006570_create_task_table.js, 20180722006688_create_attachment_table.js, 20181024220134_create_action_table.js, 20181112104653_create_notification_table.js, 20220523131229_add_image_to_attachment_table.js, 20220713145452_add_position_to_task_table.js, 20220725150723_add_language_to_user_account_table.js, 20220729142434_add_index_on_type_to_action_table.js, 20220803221221_add_password_changed_at_to_user_account_table.js, 20220815155645_add_permissions_to_board_membership_table.js, 20220906094517_create_session_table.js, 20221003140000_@.js, 20221223131625_preserve_original_format_of_images.js, 20221225224651_remove_board_types.js.js, 20221226210239_improve_quality_of_resized_images.js, 20230108213138_labels_reordering.js, 20230227170557_rename_timer_to_stopwatch.js, 20230809022050_oidc_with_pkce_flow.js, 20240721171239_languages_with_country_codes.js, 20240812065305_make_due_date_toggleable.js, 20240831195806_additional_http_only_token_for_enhanced_security_in_browsers.js, 20250131202710_add_list_color.js
planka-1 | at validateMigrationList (/app/node_modules/knex/lib/migrations/migrate/Migrator.js:567:11)
planka-1 | at Migrator.latest (/app/node_modules/knex/lib/migrations/migrate/Migrator.js:69:7)
planka-1 | at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
planka-1 | at async /app/db/init.js:14:5
planka-1 |
planka-1 | Node.js v18.20.8
planka-1 exited with code 1
@meltyshev commented on GitHub (May 19, 2025):
Hi! Yes, this is still a pre-release version, but it's ready to use and shouldn't contain any major bugs. We're addressing a few remaining issues and will release the final version soon.
Hi! This is intentional. The Project Manager role has access to all users in the system, as it allows inviting other managers and users to boards. However, we can add more separation if really needed - for example, by adding a switch when selecting the Project Manager role to disable project creation.
@meltyshev commented on GitHub (May 19, 2025):
Hi! This could happen if you're running
db:migrateinstead ofdb:upgrade, or if you forgot to run the upgrade script - the upgrade doesn't happen automatically.This answer might help:
@keksie commented on GitHub (May 19, 2025):
That'd be great if such a switch existed!
@jaimedmp commented on GitHub (May 19, 2025):
I have re-run the migration/upgrade. Below are the details:
https://github.com/jaimedmp/planka-upgrade-to-v2-error/blob/main/log
@jaimedmp commented on GitHub (May 19, 2025):
This is my V1 docker compose file content
This is my V2 docker compose file content
@meltyshev commented on GitHub (May 19, 2025):
Thanks for posting the logs. It looks like you've hit the limit for how much data can be inserted in a single query. I'm currently investigating how to resolve it.
@meltyshev commented on GitHub (May 19, 2025):
@jaimedmp I've pushed the fix, but it hasn't been released as a new version yet. However, you can try it out using the
nightlyversion and then switch back to the2.0.0-rc.2image tag. To do so, please follow these steps:2.0.0-rc.2tag, usenightly.2.0.0-rc.2and rundocker compose pull.docker compose up -d.UPD: Also, please don't forget to change the
SECRET_KEYsince it has been exposed here.@jaimedmp commented on GitHub (May 20, 2025):
I really appreciate this project. Thank you for the fix. It successfully upgraded to V2.
noted on the SECRET_KEY change.
@HannesOberreiter commented on GitHub (May 21, 2025):
Thanks for the release and thanks for keeping it open source.
@Haegar333 commented on GitHub (May 28, 2025):
Hello!
Thank you for v2!
But i am a little troubled with notifications. Is apprise already activated in planka now? I can´t get it to work.
@meltyshev commented on GitHub (May 28, 2025):
Hi! It's already installed - no further setup is needed besides configuration. You need to open User Settings → Notifications to configure notifications per user, or Board Settings → Notifications to configure them per board. Here's a link to the Apprise docs: https://github.com/caronc/apprise/wiki (it should also be clickable in the Notifications tab).
@Haegar333 commented on GitHub (May 28, 2025):
Thank you, got it to work in the meantime. 1&1 is sometimes picky with the ports to use...
Is there an option to set the same Apprise service for every user, as a standard?
Edit:
Further question:
Is there a variable that i can use to automate the "to" address? User accounts have the email address, there the emails should go.
And when is an email send?
@talondnb commented on GitHub (Jun 1, 2025):
I'm a little confused by this; I typically setup email notifications and have done so in the docker-compose.yml file using the email parameters. Will this not work on its own or do I still have to setup using apprise (which seems redundant)?
@Haegar333 commented on GitHub (Jun 1, 2025):
I got it working for me now.
The config lines in the docker-compose are obsolet now.
You have to compile a shoutrrr link fitting your system and insert it in the gui config page.
@talondnb commented on GitHub (Jun 2, 2025):
@meltyshev, can you confirm this? Is that compose file supposed to be obselete?
@meltyshev commented on GitHub (Jun 2, 2025):
Yes, except for the
SMTP_*variables - they can still be configured. But in my opinion, receiving an email for every action isn't a nice way to get notified. It would be better to group them and send a daily summary (for example) and use Apprise (in the GUI) for instant notifications.@InFeRnOw commented on GitHub (Jun 19, 2025):
Hello, my company has really been loving Planka. However, we noticed that we are unable to add a user as manager to a project unless he is admin of Planka. Is this a bug ? It's kinds of pointless to have managers for projects if you need to be admin to be a manager, as admins already have full rights.
Also, our users authenticate via SSO and we are unable to edit their roles in Planka which can make sense as it's our IAM who should manage roles but we are limited to only admin or user. Any plans for more fine-grained permissions ?
Lastly, unless being an admin, a user cannot create his own project, which I suppose is a bug or it wouldn't make sense.
Really love the project, thank you all for delivering such an amazing kaban solution !
@meltyshev commented on GitHub (Jun 21, 2025):
Hi! Thanks for the kind words.
In PLANKA v2, we introduced a new global role called Project Owner. A user with this role can create projects and act as a project manager, but they are not an admin. To assign this role automatically via SSO, you need to configure the
OIDC_PROJECT_OWNER_ROLESenvironment variable and set it to the corresponding role value from your identity provider.By the way, I just checked the compose file and realized we forgot to include the new OIDC-related variables (same goes for the documentation). Thanks for pointing that out! I'll make sure to fix it as soon as I'm back from vacation.
@kristian-94 commented on GitHub (Jun 24, 2025):
Thanks for this great tool. Is v2 supposed to have all features of v1 or are they being added over time? I'm assuming if I see something missing to just wait for new releases
@mrforsythexeter commented on GitHub (Jun 24, 2025):
Your docs basically get you to install the latest RC version, since you are pulling directly from the repo and have the admin create command for npm, however my experience so far is that you are right to tag it as RC as it's not ready.
After adding a board in my installation (completely fresh), the plus icon for adding more boards or list on a board is gone. Which means I need to throw it away and stack again. I assume this is not expected behaviour considering your install instructions want you to install this version, however your docker "latest" tag appears to be on 1.26 still?
@meltyshev commented on GitHub (Jul 3, 2025):
Thanks for the question! v2 is intended to include everything from v1, though a few features are still missing - for example, the ability to run the app under a custom
/path.If you can't see the plus button to add more boards, it's likely because Edit Mode is disabled. You can enable it by toggling the Lock icon in the header (near the Bell icon). We've received a few similar questions and are considering ways to make this more intuitive.
As for the RC version - it's stable and ready for production use. We'll release the final version and tag it as
latestonce everything else is ready, including the new website, updated demo, and hosting options (probably need a few more weeks to wrap things up).@erwinsonp commented on GitHub (Jul 10, 2025):
Hi, I just came across this awesome project and wanted to try it out.
However, the docs say that to install v2 RC, I should have v1.26.2.
I will try to install straight to v2 since I haven't installed it yet, but I just wanted to ask if I will run into issues if I do not upgrade from 1.26 (like maybe it expects a database migration is done, etc)? I'm especially worried for problems that would not be obvious until I have a couple of projects already. Thank you
@Haegar333 commented on GitHub (Jul 10, 2025):
I went straight to 2 in a new install without problems.
@talondnb commented on GitHub (Jul 11, 2025):
Can you please explain how I can do this?
I tried this today and assigned a user project owner in Authentik which then propagated to planka, however, that user couldn't modify details at the high level (title, background,etc. and yes, had the lock unlocked too).
@phroun commented on GitHub (Jul 13, 2025):
I upgraded to V2, following the upgrade-to-v2 guide, but now I see a blank page when trying to access planka, and no errors showing in the logs. When I view the console output of the blank page in browser debugger, I see a series of "Mixed Content: The page at 'https://my-domain-here.org/planka/' was loaded over HTTPS, but requested an insecure stylesheet" wanings, and those assets seem to have redirect to my domain's 404 page. Is it possible BASE_URL not being honored in the environment?
I'm not sure what to do at this point, or what steps are necessary to take to restore from my backup and downgrade back to V1 ... I seem to be dead in the water.
@meltyshev commented on GitHub (Jul 15, 2025):
Hi! If I understand your question correctly, it doesn't matter whether you do a fresh install of the v2 RC or upgrade from v1 - the database structure and everything else will be the same.
@meltyshev commented on GitHub (Jul 15, 2025):
Apprise can be configured per user and per board. For example, to configure notifications per board (so you receive all board updates), open Board Settings (enable Edit Mode and click the pencil icon next to the board name). Then, go to the Notifications tab and enter the service URL for the desired notification service. You can find supported services and how to format the URL in the Apprise documentation.
The global Project Owner role doesn't automatically grant full editing rights to all projects or boards. To modify project details (such as the title, background, etc.), a user must be a manager of that specific project.
A user becomes a manager either by creating the project or by being added as a manager by another existing manager.
@meltyshev commented on GitHub (Jul 15, 2025):
Hi! Sorry about that - the ability to host under a
/pathwas removed during the migration to the new build system, since it's not compatible with the previous code that rewrites paths. As a workaround for now, if possible, you can use a subdomain instead of a path - for example,https://planka.my-domain-here.org. I'll look into this today, it might not be too difficult to reintroduce support for it.Here's the related issue for reference: https://github.com/plankanban/planka/issues/1156.
@phroun commented on GitHub (Jul 15, 2025):
Thanks, I succeeded in switching to using a subdomain. You might want to at least add a note about this in the upgrade instructions so that it doesn't trip anyone else up.
@Kf637 commented on GitHub (Aug 1, 2025):
Are the still plans to add #602?
@meltyshev commented on GitHub (Aug 2, 2025):
Yes, but it's hard to say when it will be added. Right now, we're focused on releasing the final v2 version, launching the new website, and starting to offer services.
@BeyondVertical commented on GitHub (Oct 29, 2025):
Do you have a rough ETA for version 2?
@MohsenSameti commented on GitHub (Dec 1, 2025):
do you intend to support rtl? (mixing rtl with english does not work)
@phroun commented on GitHub (Dec 1, 2025):
What is the upgrade path for those of us who are already on 2.0.0.rc3 to get to the final release? Also, I use Planka every day, thank you for your great work.
@BeyondVertical commented on GitHub (Dec 23, 2025):
So, any news for the release of version 2? Obviously 2026, but which quarter for example?
@sknowledge1 commented on GitHub (Jan 27, 2026):
+1! we're on RC4 now, when is it going to be released?