Project should not close, if project task has attachment man/key milestone task is open state
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
How can we prevent a project from being closed when there are open key milestone tasks or tasks with mandatory attachments that have not yet been completed?
Scenario: A project should not move to the closed status if:
- Any key milestone task is still in an Open state.
- Any task with a mandatory attachment requirement is incomplete or the required attachment has not been uploaded.
Has anyone implemented a validation or business rule to enforce this behavior? What is the recommended approach?
Or, as a requirement statement:
Requirement: The system must prevent project foreclosure when at least one key milestone task remains open or when a task with mandatory attachments is not completed with the required attachments.
0 REPLIES 0