✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount
✨ New Plugin Alert ✨ SleekRank is now available with €50 launch discount

SleekView Kanban for JetEngine Pro

SleekView Kanban reads JetEngine Pro custom content type rows, groups them by a CCT custom status field, and lets editors drag entries between Pending, In progress, Resolved, and Closed. JetEngine listings, queries, and dynamic visibility re-evaluate on every drop.

♾️ Lifetime License available

SleekView Kanban board for JetEngine Pro

Why JetEngine CCTs need a workflow view

JetEngine Pro lets builders register custom content types stored in dedicated database tables, with their own schema and a meta engine that writes field values directly to the CCT table rather than to wp_postmeta. JetEngine Pro adds query builders, listings, dynamic visibility, and a glossary system holding option lists used by Select and Radio fields, including a custom status field that drives a CCT row through a workflow.

The default JetEngine CCT admin shows entries in a dedicated table with sortable columns. That works for a quick spot check but breaks down once a builder manages hundreds of CCT rows across several content types, especially when each row carries a status field that drives its workflow. Counting how many CCT rows are Pending, In progress, Resolved, or Closed requires scanning a sortable column.

SleekView Kanban points at the JetEngine Pro CCT, groups rows by the custom status field, and renders Pending, In progress, Resolved, and Closed as lanes. Each card shows the JetEngine meta you pick from the same field engine the listings use. Dragging writes through the JetEngine CCT update API, so JetEngine listings, queries, and dynamic visibility re-evaluate on the next render exactly as on a normal save.

Workflow

From JetEngine CCT table to kanban

1

Pick the JetEngine Pro CCT

Install SleekView and pick a JetEngine Pro custom content type as the data source. SleekView reads the JetEngine meta engine config and detects every CCT field, including the glossary Select holding the status.
2

Group by the CCT status field

Set the group-by field to the CCT custom status field that holds the workflow value. SleekView renders Pending, In progress, Resolved, and Closed as lanes using glossary labels, with a live count of CCT rows per lane.
3

Pick card meta from JetEngine

Choose which JetEngine CCT fields appear on the card front. Text, Number, Date, Media, User, and Posts relation fields render directly, and heavy fields open in a side panel so the lane stays scannable.
4

Enable drag-and-drop CCT writes

Flip drag-and-drop on and SleekView writes the new status through the JetEngine CCT update API. JetEngine listings, query builder grids, and dynamic visibility re-evaluate on the next page render like a normal save.

Sample board

Sample JetEngine CCT workflow board

A SleekView Kanban grouping JetEngine Pro CCT rows by the custom status field, with cards showing the assigned User, the due Date, and any linked Posts.
Pending
36
Support ticket by Maya at harbor co
owner Anna, opened today via form
Support ticket by Sam at summit run
owner Lead Anna, opened yesterday
Support ticket by Priya at studio go
owner editor Sam, opened 2d ago
In progress
18
Support ticket by Leo at downtown link
owner Lead Anna, day 4 of work
Support ticket by Marcus at atelier go
owner editor Sam, sprint 2 work now
Support ticket by Chris at tutor link
owner Lead Anna, week 2 of work
Resolved
247
Support ticket by Maya R at harbor co
resolved by Lead Anna today via API
Support ticket by Sam D at summer run
resolved by editor Chris yesterday
Support ticket by Jordan V at atelier
resolved by Lead Anna this week
Closed
412
Support ticket from harbor co work run
closed 2 weeks ago by Lead Anna lead
Support ticket from summer summit go
closed last week by editor Sam team
Support ticket from studio thirty link
closed yesterday by Lead Anna review

Comparison

Default JetEngine CCT table vs SleekView

Default JetEngine CCT table

  • CCT rows show as a flat sortable table with no grouping by status across rows
  • Listings render the visible CCT state but never the queue shape of the workflow
  • Advancing a CCT status means opening each row and editing the Select by hand
  • No bulk advance across a list of CCT rows from the default JetEngine admin page
  • Glossary labels show only inside the field render, not as visual lanes on a board

SleekView Kanban

  • Groups JetEngine Pro CCT rows by the glossary-backed custom status field per lane
  • Drag a card to advance the workflow through the JetEngine CCT update API per row
  • Card fronts show JetEngine User, Date, Media, and linked Posts fields directly
  • JetEngine listings, queries, and dynamic visibility re-evaluate after each save
  • Capability gates restrict Closed and Resolved lanes to senior support lead roles

Features

What SleekView Kanban gives you for JetEngine Pro

Lanes from CCT glossary

JetEngine glossaries hold the option lists for CCT Select fields. SleekView reads the glossary on the custom status field and renders one lane per value with the glossary label, so the board uses the same vocabulary as the front.

Saves through CCT API

SleekView writes the new status through the JetEngine CCT update API rather than update_post_meta, since CCT rows live in dedicated tables. JetEngine listings and dynamic visibility re-evaluate after the save.

Filter by any CCT field

A filter bar narrows lanes by any JetEngine CCT field value, including Posts relations, User assignments, and Date ranges. Saved filters are per-user and per-board, so each agent scopes the dataset to their workflow.

Audience

JetEngine Pro teams that need a triage board

Support ticket CCTs

Support teams model tickets as JetEngine Pro CCT rows with a custom status field. Pending captures new tickets, In progress tracks live work, Resolved holds the audit trail, and Closed locks the row.

Agency project CCTs

Agencies model client projects as JetEngine Pro CCT rows with a custom status field. The board groups projects by status and the User field appears on each card for clean ownership across the team.

Internal task CCTs

Internal teams model tasks as JetEngine Pro CCT rows with a custom status field driving the workflow. The board doubles as the team standup with Pending, In progress, Resolved, and Closed visible.

The bigger picture

Why a kanban beats a JetEngine CCT table

JetEngine Pro is already great at displaying CCT data on the front of a WordPress site. Listings, query builders, and dynamic visibility produce beautifully arranged grids and dashboards for end users. But none of that helps the team managing the CCT rows behind the scenes.

The default JetEngine Pro admin shows CCT entries in a flat sortable table that mirrors the WordPress post list, which means the workflow team loses every visual cue about how much work is in each lane. A kanban board fixes that shape on the admin side. The same JetEngine glossary that drives front-of-site labels drives the lane structure on the board, the same JetEngine CCT fields that listings show on the front appear on the card front, and drag-and-drop turns a status advance into a single gesture that writes through the JetEngine CCT update API.

JetEngine listings, queries, and dynamic visibility re-evaluate after each save as on a normal admin CCT edit.

Questions

Common questions about SleekView Kanban for JetEngine Pro

SleekView reads directly from the existing JetEngine Pro CCT tables through the plugin's data layer. No data is duplicated and no shadow tables are added. Uninstalling SleekView leaves every CCT row exactly where JetEngine Pro wrote it on save without any leftover artifacts.

 

Yes. SleekView reads the JetEngine glossary attached to the custom status field and uses the glossary label as the lane title. CCT Select field values on the card front also resolve to their glossary labels, so the same vocabulary used on the front of the site appears on the board.

 

Yes. SleekView writes through the standard JetEngine CCT update API, which triggers WordPress save hooks and JetEngine cache invalidation just like a normal CCT admin save. Listings, query builder grids, and dynamic visibility re-render on the next page load across the front of the site.

 

Yes. SleekView supports per-user filters on any JetEngine User field on the CCT row, so each agent sees only cards where the assigned User field matches their account. The same board configuration powers every agent view, while leadership sees the unfiltered version with the global queue.

 

Yes. SleekView evaluates JetEngine dynamic visibility per card based on the current user and the CCT row state. Fields hidden by dynamic visibility on the front stay hidden on the card, and they reappear when a card moves into a status that reveals them via the JetEngine rule engine.

 

SleekView reads the JetEngine glossary on every render, so a new value shows up automatically as a new lane on the board with a count of zero CCT rows. You can drag the lane into the desired position, assign a color, and start using it without reconfiguring the board view.

 

Yes. SleekView respects WordPress capabilities and supports per-lane drop rules. Junior agents can move cards into Pending and In progress, while only senior support leads can drop a card into Closed with the corresponding audit row written into the CCT table on the save.

 

SleekView reads and writes the existing JetEngine Pro CCT tables. No shadow tables are created and uninstalling SleekView leaves every CCT row, glossary value, and meta field where JetEngine Pro wrote it on save. View config sits in a small options row for clean teardown.

 

Pricing

More than 1000+
happy customers

Explore our flexible licensing options tailored to your needs. Upgrade your license anytime to access more features, or opt for a lifetime license for ongoing value, including lifetime updates and lifetime support. Our hassle-free upgrade process ensures that our platform can grow with you, starting from whichever plan you choose.

Starter

€79

EUR

per year

  • 3 websites
  • 1 year of updates
  • 1 year of support

Pro

€149

EUR

per year

  • Unlimited websites
  • 1 year of updates
  • 1 year of support

Lifetime ♾️

Most popular

€249

EUR

once

  • Unlimited websites
  • Lifetime updates
  • Lifetime support

...or get the Bundle Deal
and save €250 🎁

The Bundle (unlimited sites)

Pay once, own it forever

Elevate your WordPress site with our exclusive plugin bundle that includes all of our premium plugins in one package. Enjoy lifetime updates and lifetime support. Save significantly compared to buying plugins individually.

What’s included

  • SleekAI

  • SleekByte

  • SleekMotion

  • SleekPixel

  • SleekRank

  • SleekView