Version 2 has been released!

[nickbe]

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]

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]

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:

root@planka:/var/www/planka# npm run db:upgrade

> db:upgrade
> node db/upgrade.js

Upgrading database...
error: insert into "user_account" ("avatar", "created_at", "default_editor_mode", "default_home_view", "default_projects_order", "email", "enable_favorites_by_default", "id", "is_deactivated", "is_sso_user", "language", "name", "organization", "password", "password_changed_at", "phone", "role", "subscribe_to_card_when_commenting", "subscribe_to_own_cards", "turn_off_recent_card_highlighting", "updated_at", "username") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, $19, $20, $21, $22), ($23, $24, $25, $26, $27, $28, $29, $30, $31, $32, $33, $34, $35, $36, $37, $38, $39, $40, $41, $42, $43, $44), ($45, $46, $47, $48, $49, $50, $51, $52, $53, $54, $55, $56, $57, $58, $59, $60, $61, $62, $63, $64, $65, $66), ($67, $68, $69, $70, $71, $72, $73, $74, $75, $76, $77, $78, $79, $80, $81, $82, $83, $84, $85, $86, $87, $88), ($89, $90, $91, $92, $93, $94, $95, $96, $97, $98, $99, $100, $101, $102, $103, $104, $105, $106, $107, $108, $109, $110) - relation "user_account" does not exist
    at Parser.parseErrorMessage (/var/www/planka/node_modules/pg-protocol/dist/parser.js:285:98)
    at Parser.handlePacket (/var/www/planka/node_modules/pg-protocol/dist/parser.js:122:29)
    at Parser.parse (/var/www/planka/node_modules/pg-protocol/dist/parser.js:35:38)
    at Socket.<anonymous> (/var/www/planka/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12)
    at readableAddChunk (node:internal/streams/readable:341:9)
    at Readable.push (node:internal/streams/readable:278:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
  length: 111,
  severity: 'ERROR',
  code: '42P01',
  detail: undefined,
  hint: undefined,
  position: '13',
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'parse_relation.c',
  line: '1381',
  routine: 'parserOpenTable'
}

[meltyshev]

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.

Thanks for reporting this! We'll definitely look into it and re-test each step.

[meltyshev]

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:

root@planka:/var/www/planka# npm run db:upgrade

> db:upgrade
> node db/upgrade.js

Upgrading database...
error: insert into "user_account" ("avatar", "created_at", "default_editor_mode", "default_home_view", "default_projects_order", "email", "enable_favorites_by_default", "id", "is_deactivated", "is_sso_user", "language", "name", "organization", "password", "password_changed_at", "phone", "role", "subscribe_to_card_when_commenting", "subscribe_to_own_cards", "turn_off_recent_card_highlighting", "updated_at", "username") values ($1, $2, $3, $4, $5, $6, $7, $8, $9, $10, $11, $12, $13, $14, $15, $16, $17, $18, $19, $20, $21, $22), ($23, $24, $25, $26, $27, $28, $29, $30, $31, $32, $33, $34, $35, $36, $37, $38, $39, $40, $41, $42, $43, $44), ($45, $46, $47, $48, $49, $50, $51, $52, $53, $54, $55, $56, $57, $58, $59, $60, $61, $62, $63, $64, $65, $66), ($67, $68, $69, $70, $71, $72, $73, $74, $75, $76, $77, $78, $79, $80, $81, $82, $83, $84, $85, $86, $87, $88), ($89, $90, $91, $92, $93, $94, $95, $96, $97, $98, $99, $100, $101, $102, $103, $104, $105, $106, $107, $108, $109, $110) - relation "user_account" does not exist
    at Parser.parseErrorMessage (/var/www/planka/node_modules/pg-protocol/dist/parser.js:285:98)
    at Parser.handlePacket (/var/www/planka/node_modules/pg-protocol/dist/parser.js:122:29)
    at Parser.parse (/var/www/planka/node_modules/pg-protocol/dist/parser.js:35:38)
    at Socket.<anonymous> (/var/www/planka/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12)
    at readableAddChunk (node:internal/streams/readable:341:9)
    at Readable.push (node:internal/streams/readable:278:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
  length: 111,
  severity: 'ERROR',
  code: '42P01',
  detail: undefined,
  hint: undefined,
  position: '13',
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'parse_relation.c',
  line: '1381',
  routine: 'parserOpenTable'
}

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...

Should we post the issues facing the upgrade process here or in seperate issues?

Here it's totally fine, will be easier to handle :)

[meltyshev]

The docs have been updated. Tested everything again and didn’t encounter the same issues.

[FibreFoX]

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]

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]

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]

Some short comments to this:

I have a question: is there a reason, that comments are now "right-aligned"?

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:

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

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.

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?

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]

First, thanks for the feedback. We are happy to have it.

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)

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.

• 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)

This is still work in progress. The difference will be much more obvious in due time.

• The 'Board', 'Archive' and 'Trash' views have no easily discernible differences (only the top right icon)

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.

• 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)

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.

• 'Archived' cards don't look "Archived" (aka old/aged)

Good point. It also falls under the category "work in progress". We simply didn't find the time to really design something better.

• 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)

It's on our list for later. But I feel the same.

• 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).

Yeah we like the new editor too. It solved so many issues at once 😁
We plan something like that already

[meltyshev]

• Can't convert a 'Shared' (existing v1) project to a 'Private' project

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]

The docs have been updated. Tested everything again and didn’t encounter the same issues.

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 planka we should change the directory to /var/www/planka again otherwise npm will fail ofc ;)

[meltyshev]

after switching to the planka user with sudo -i -u planka we should change the directory to /var/www/planka again otherwise npm will fail ofc ;)

Oops 🙈 Thanks for mentioning that!