Enforce Unique Task Names with Auto Number

Feature Request: Enforce Unique Task Names with Auto Numbering

Summary:
Add a proposal-level and template-level setting to enforce unique task names, even when auto-numbering is enabled. When this setting is active, the system should use only the task name (not the task number) to detect duplicates during import and overwrite operations.

Problem Statement:
Today, when importing tasks with overwrite enabled and auto-numbering in place, the system treats a task as the same only if both the task number and the task name match. Because task numbers are often auto-generated and may differ between systems or exports, users must manually align both the task number and the name. This is time-consuming, error-prone, and often results in unintended new tasks being created instead of expected updates to existing tasks.

Proposed Solution:
Introduce a setting in proposal properties and templates called “Enforce unique task names.”
When this setting is enabled:

• The system should use the task name as the primary (or sole) key for duplicate detection during imports and overwrite operations.

• Auto-generated task numbers should be ignored for matching/duplicate handling logic.

• Users cannot enter tasks on the proposal that have the same name.

• If an imported task name matches an existing task name, the system should treat it as an update to that existing task (subject to overwrite rules).

• If an imported task name does not match any existing task name, the system should create a new task.

• Provide clear validation or error messaging if multiple existing tasks share the same name, so users understand any conflicts and can resolve them.

Benefits:
Reduces manual effort required to align task numbers before import, especially when numbers are auto-generated.
Decreases the risk of accidentally creating duplicate tasks during import and overwrite workflows.
Improves data integrity by ensuring a consistent, name-based matching strategy when desired.
Streamlines common import scenarios where users logically think in terms of task names rather than system-generated task numbers.
Enhances user confidence and satisfaction when working with large or repeated task imports.