[Feature Request] Kanban module: Integration Hub: Link Kanban Cards to Core Tasks or Wiki Pages via Space Admin UI

[JK742020]

Description

To prevent data duplication and turn the Kanban module into a central hub, it would be highly valuable to link Kanban cards directly to existing HumHub core content (Tasks or Wiki pages).

Our primary focus and favored approach is full automation (Variant 2), as it creates the cleanest workflow and keeps the Card UI simple.

Proposed Solution / Workflow

Add a data source toggle right into the Space Admin UI:

[ ] Integrate HumHub Tasks Core

• Admin Step: Select a Target Space and a core task list from that space.
• [FAVORED] Card Step (Variant 2 - Automated Creation): When a new task is created in that list, a new Kanban card is automatically generated in the first column of the board. This is our preferred solution as it requires no manual action and keeps the Card UI clean.
• Optional / Secondary: Card Step (Variant 1 - Manual Dropdown): A dropdown inside the card to link existing tasks manually (only if automated creation is not preferred by the developer).

[ ] Integrate HumHub Wiki-Pages

• Admin Step: Select a Target Space and a specific Parent Wiki Page from that space.
• [FAVORED] Card Step (Variant 2 - Automated Creation): When a new sub-page is created under that parent page, a new Kanban card is automatically generated in the first column of the board. This is our preferred solution as it creates a perfect "zero-click" workflow.
• Optional / Secondary: Card Step (Variant 1 - Manual Dropdown): A dropdown inside the card to link existing sub-pages manually.

Behavior in the Card UI (Once linked / Automated)

• Direct Access: The card provides a link/action to open the linked Wiki/Task directly inside a native HumHub modal (overlay).
• Title Sync (Read-Only): The Kanban card automatically inherits the title of the linked Wiki/Task. To prevent data inconsistency, the title field becomes non-editable inside the card UI and can only be changed within the source Wiki page / Task (via the Direct Access modal).
• Smart UI Adaption: On automated boards/columns, the manual "Add Card" button is disabled, ensuring that cards are only generated through incoming core content.
• Kanban-Native Flexibility: Despite the title lock, users can still fully utilize Kanban-specific features on the card:
  • Managing and assigning Labels (e.g., "Urgent", "Spring Season").
  • Utilizing the card's internal Description field for team-internal notes and micro-updates, separating them from the official Wiki content.
• AJAX Refresh: Closing the native HumHub modal triggers an AJAX title/content-refresh on the board to keep everything synced without full page reloads (F5).
• Fallback (Standard Mode): If the automation toggle in the Space Admin UI is disabled, the Kanban board operates completely as usual (fully editable titles, manual card creation, etc.).

Why this is useful

It allows heavy users of the Tasks or Wiki modules (especially those feeding data via external automated webforms like WPForms) to use the Kanban board as a lightweight, high-performance visual dashboard without duplicating database records.

By prioritizing the automated card creation, new content triggers an instant visual update on the board. Project managers immediately see new items pop up without a single manual copy-paste step.

Most importantly, this approach turns the module into a flexible hybrid system:
Spaces that do not require automation can still use all standard, manual Kanban features as before. This ensures that the module remains a universal project management tool for everyone, while offering advanced automated workflows for power users.

[JK742020]

I updated the description above. I made it clear that the automated card creation (Variant 2) is my absolute favorite and priority for this feature request. It creates a true "zero-click" workflow (great for automated content like WPForms feeding into the Wiki) and keeps the implementation simpler for you, since we don't necessarily need a complex manual dropdown UI inside the cards right away.

[JK742020]

Update: I have updated the main description to refine the behavior of the Card UI when automation is active.

To prevent any data inconsistency, the card title should become read-only and sync directly from the source Wiki/Task (accessible via the direct modal link). However, teams can still use Kanban-native features like Labels and the Description field for internal notes on the card.

If the automation is disabled, the board will fall back to its standard, fully manual behavior. This keeps the module universal and flexible for all types of use cases. Let me know what you think!

[JK742020]

I also noticed the current "Priority" dropdown and submitted a separate, complementary feature request here to see if we can evolve this into a single, open Label system. This would keep the UI super clean while adding massive flexibility for team workflows! #25 (comment)

[JK742020]

Update: I just opened a architectural proposal in #26 to discuss splitting the core Kanban board and this advanced Workflow/Automation layer into two separate modules for better maintainability and permission control.

[ArchBlood]

I've implemented and am starting testing as we speak;

[JK742020]

Looks great too! Thanks!

What is target column?
In my scenario it would look like this.

Wiki: I would like to have cards created automatically for all child-wiki-pages of "New Requests from Wordpress"

• New Requests from Wordpress (ID 24 for example)
  • Request 1
  • Request 2
• Locations for programs
  • location 1
  • location 2

Same thing with tasks. Cards should be created for all tasks of the selected list (i.e. New task list).

• New task list (ID 28 for example)
  • task 1
  • task 2
• Another task list
  • task 1
  • task 2

As I understand ID in my scenario ID 24 or 28 need to be selected in the second pulldown. But what to select in the third pulldown?

Another idea which came in mind at the moment:

Wouldn't it be great to have a + underneath the first line of pulldowns to add another Space/ID etc.? and a bin-icon at the end of the list to delete an already created destination. If this is too much effort I'm still happy with one source per kanban. If it's not a big deal to implement it would be cool I think.

[ArchBlood]

Looks great too! Thanks!

What is target column?
In my scenario it would look like this.

Wiki: I would like to have cards created automatically for all child-wiki-pages of "New Requests from Wordpress"

• New Requests from Wordpress (ID 24 for example)
  • Request 1
  • Request 2
• Locations for programs
  • location 1
  • location 2

Same thing with tasks. Cards should be created for all tasks of the selected list (i.e. New task list).

• New task list (ID 28 for example)
  • task 1
  • task 2
• Another task list
  • task 1
  • task 2

As I understand ID in my scenario ID 24 or 28 need to be selected in the second pulldown. But what to select in the third pulldown?

Another idea which came in mind at the moment:

Wouldn't it be great to have a + underneath the first line of pulldowns to add another Space/ID etc.? and a bin-icon at the end of the list to delete an already created destination. If this is too much effort I'm still happy with one source per kanban. If it's not a big deal to implement it would be cool I think.

Parent + child wiki will be slightly more difficult, it is better to just handle them the same way.

[JK742020]

Parent + child wiki will be slightly more difficult, it is better to just handle them the same way.

Ah! Now I understand. I select the ID of the list/wiki and cards are created from all childs of the wiki/list. That's perfect! I didn't understand that Target column is within the Kanban ;) Now I got it. Yes, that's the way it's intended.

What about the idea with the + to choose different lists/wikis?

[JK742020]

Concerning ID: Wouldn't it be much more user friendly to offer the name of the lists/wiki pages instead of IDs. I guess users don't know the IDs of the list or where to look for them!