Multi-Assignee Support for Task Bulk Import

Enhancement Voting Tasks
1

Name of Feature/Request: Multi-Assignee Support for Task Bulk Import

What financial, time savings, or quality of life improvements will occur with this:

  1. Time Savings: Eliminates the need for manual post-import edits. Importing large project schedules or recurring task lists with collaborative tasks currently requires opening each imported task individually to manually add secondary team members.
  2. Financial / Operational Efficiency: Significantly reduces project setup overhead and labor costs when onboarding new projects, migrating data, or building out complex milestone templates.
  3. Quality of Life & Accuracy: Prevents missed deadlines and miscommunication caused by human error, ensuring no team member is accidentally left off a task during manual updates after a bulk import.

Attempted solutions so far:

  1. Manual Task Post-Processing: Importing the task list assigned to a single primary owner, then manually searching, opening, and editing each task in Striven to assign additional users. This is extremely time-consuming for large imports (50+ tasks).
  2. Creating Duplicate Task Rows: Attempting to duplicate task rows in the CSV import file for each user, which results in multiple duplicate tasks rather than a single collaborative task assigned to multiple people.

Digging deep - Any additional Why behind this request / How was this accomplished before Striven:

  1. The “Why”: Modern workflows frequently rely on shared accountability, where tasks (e.g., joint site audits, team reviews, multi-person approvals, or pair programming) naturally belong to two or more individuals. While Striven’s UI natively supports assigning multiple users to a task, the bulk import tool artificially restricts this functionality to a 1:1 mapping, creating a bottleneck during project setup.
  2. How it was accomplished before / Industry Standard: Standard project management platforms and import tools allow multi-value fields in CSV/Excel imports by using delimiters (e.g., comma, semi-colon, or pipe-separated values like john@company.com, jane@company.com or User ID 101 | User ID 102). The import parser reads the delimited string and maps each user directly to the task’s multi-select assignee field upon validation.