Content
View differences
Updated by Niels Lindenthal 24 days ago
**Dynamic input masks on status transition**
* When user attempts to transition an work package to a new status, system displays a modal/dialog with new (required) fields
* Modal shows only fields relevant to the target status (not all issue fields)
* User cannot complete transition until all mandatory fields are filled with valid data
* System provides clear validation messages for incomplete or invalid fields
* User can cancel transition and return to work package without saving changes
* Define conditions for transitions to cover edge cases, e.g. you can go from A to B, but depending on XYZ
**Status-specific mandatory fields configuration**
* Administrator can define mandatory fields per status per work package type via workflow configuration
* Definition happens within project settings and not within global admin settings
* Administrator can specify field requirements for:
* Entering a status (fields required when transitioning TO this status)
* Exiting a status (fields required when transitioning FROM this status)
* System supports all standard field types
* Custom fields are fully supported
**Read-Only field controls**
* Administrator can configure fields to become read-only based on:
* Current issue status
* Specific field values (e.g., when "Approved" = Yes)
* Read-only fields are visually indicated (greyed out, lock icon)
* System prevents editing of read-only fields via UI and API
* Administrator can define exceptions (e.g. Project Admin can always edit) (TBD)
* Read-only rules apply consistently across:
* Issue view/edit screens
* Bulk edit operations
* API requests
* Automation rules
* Hover tooltips explain why fields are read-only
**Configuration interface**
* Workflow editor includes "Field Behavior" configuration tab for each status
* Visual workflow diagram indicates statuses with special field requirements (badge/icon)
* Configuration wizard guides administrator through setup:
* Select status
* Define (mandatory) fields
* Set required actions
* Configure approvers (if applicable)
* Define read-only fields
* Configuration supports copy/paste between statuses and issue types
* Preview mode shows what users will see during transition
* When user attempts to transition an work package to a new status, system displays a modal/dialog with new (required) fields
* Modal shows only fields relevant to the target status (not all issue fields)
* User cannot complete transition until all mandatory fields are filled with valid data
* System provides clear validation messages for incomplete or invalid fields
* User can cancel transition and return to work package without saving changes
* Define conditions for transitions to cover edge cases, e.g. you can go from A to B, but depending on XYZ
**Status-specific mandatory fields configuration**
* Administrator can define mandatory fields per status per work package type via workflow configuration
* Definition happens within project settings and not within global admin settings
* Administrator can specify field requirements for:
* Entering a status (fields required when transitioning TO this status)
* Exiting a status (fields required when transitioning FROM this status)
* System supports all standard field types
* Custom fields are fully supported
**Read-Only field controls**
* Administrator can configure fields to become read-only based on:
* Current issue status
* Specific field values (e.g., when "Approved" = Yes)
* Read-only fields are visually indicated (greyed out, lock icon)
* System prevents editing of read-only fields via UI and API
* Administrator can define exceptions (e.g. Project Admin can always edit) (TBD)
* Read-only rules apply consistently across:
* Issue view/edit screens
* Bulk edit operations
* API requests
* Automation rules
* Hover tooltips explain why fields are read-only
**Configuration interface**
* Workflow editor includes "Field Behavior" configuration tab for each status
* Visual workflow diagram indicates statuses with special field requirements (badge/icon)
* Configuration wizard guides administrator through setup:
* Select status
* Define (mandatory) fields
* Set required actions
* Configure approvers (if applicable)
* Define read-only fields
* Configuration supports copy/paste between statuses and issue types
* Preview mode shows what users will see during transition