Join below

By submitting this form you acknowledge our Privacy Statement.

Planview Labs: Global Card Types

Join Our Labs Program!

We're introducing Global Card Types in AgilePlace. This new capability lets you define card types once at the organization level and apply them consistently across all your boards.

Who is a great fit for this labs?
Admins or managers managing multiple boards who have felt the pain of manually recreating or synchronizing card types and who are willing to use Global Card Types on active boards and tell us honestly what works and what doesn't.

Main Advantages:

  • Define card types once, available across every board in your organization
  • Eliminate manual effort keeping card type definitions in sync
  • Consistent naming and structure so reports work the way you expect
  • Reduce per-board admin overhead across teams and value streams

What we're trying to learn:

  • When do teams need global card types vs. local flexibility — and where does the line fall?
  • What would a safe migration from existing board-local types need to look like?
  • What friction should we solve before extending this to other attributes?

Your feedback directly shapes the migration path for existing customers and the broader Global Attributes roadmap.

We're introducing Global Card Types in AgilePlace. This new capability lets you define card types once at the organization level and apply them consistently across all your boards.

Who is a great fit for this labs?
Admins or managers managing multiple boards who have felt the pain of manually recreating or synchronizing card types and who are willing to use Global Card Types on active boards and tell us honestly what works and what doesn't.

Main Advantages:

  • Define card types once, available across every board in your organization
  • Eliminate manual effort keeping card type definitions in sync
  • Consistent naming and structure so reports work the way you expect
  • Reduce per-board admin overhead across teams and value streams

What we're trying to learn:

  • When do teams need global card types vs. local flexibility — and where does the line fall?
  • What would a safe migration from existing board-local types need to look like?
  • What friction should we solve before extending this to other attributes?

Your feedback directly shapes the migration path for existing customers and the broader Global Attributes roadmap.