Skip to content

Preflight Checks need to be more specific #1267

@jhafel

Description

@jhafel

The Preflight checks are an incredible way to keep the team following Revit best practices, but the preflight checks are too vague to really make any proper changes if an issue comes up.

An example of this would be the reference planes check which told us we had 44 unnamed reference planes in our project but did not tell us any locations or how to fetch them. we went through each view and found 40 of the 44, but 4 of them are eluding us.

Another example would be the schedule checker. the preflight says we have over 100 schedules and 103 are not even on sheets, but the schedules section within Revit only shows 30 schedules overall. It would be nice to see what the preflight is considering to be a schedule. (Even if it's just a static list of schedule names that I can right-click within the project browser and search for it)

This feature is such a good tool and can't wait to see it developed further!

Metadata

Metadata

Assignees

No one assigned

    Labels

    EnhancementEnhancement request [class->Improved #{number}: {title}]Extension ChecksIssues related to pyRevit extension checks [subsystem]ToolsIssues related to pyRevit commands [subsystem]

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions