Product Features & Usage | Common Questions
How do cross-project dependencies work in Nooga Scale, and are there limitations? The cross-project dependency feature allows you to manage dependencies between projects. Users sometimes encounter errors if area paths and iteration paths are not synchronized across projects. It is important to accurately set up area and iteration structures in the parent and child projects for cross-project work. For best results, ensure that all relevant teams and projects are included in the Scale configuration and that iteration names match .
What is the best practice for setting up Nooga Scale for cross-project scenarios? When using Scale across multiple Azure DevOps projects, establish a clear hierarchy in your main (portfolio) project reflecting all contributing projects and teams. Create matching iteration names and area paths. Be aware that some features may be optimized for single-project setups rather than cross-project configurations .
How do team iterations affect analytics and reporting views? When using “Team Iterations” for an ART, mismatched start and end dates between teams can lead to iterations not displaying in the correct PI (Program Increment) views. It is advisable to align iteration cycles or adjust reporting to accommodate differing team cadences .
Does the dependency hub functionality require any special access or keys, and how can I ensure my team can evaluate it? Some organizations request additional test license keys to evaluate specific features, like the dependency hub. Contact Nooga Scale support to request access for team members as needed, ensuring that evaluators have proper permissions and activation for the relevant features .
What should I do if I get errors with area path and iteration path not being found when creating work items across projects? This issue usually results from mismatched or incomplete area and iteration path setups in the target project. Review your configuration and ensure all projects involved in cross-project planning/boards have a matching area and iteration structure defined in Nooga Scale and Azure DevOps .
Why can't I see the “Board Column” value or correct parent names in PI Objectives/Risks, and how can I make these visible? Configuration in PI Objectives and Risks tabs sometimes only displays partial information (like states or IDs). To show complete information, verify that fields like “Board Column” and “Parent” are correctly added in Nooga Scale settings. If these issues persist, contact support with details for workaround or improvements .
How do I re-order teams in Boards or customize columns/fields? Currently, team order follows alphabetical or numeric naming. You can prefix teams with numbers to influence order. Custom column or field support depends on configuration.
How can I automate flagging overdue features in red, or create complex rules for Boards? Current automation supports equals (=) operators in style rules; less-than/greater-than for dates may not be available. Consider integrating with Power Automate for advanced logic, or tag features manually. Future updates may extend automation options.
How do I incorporate external dependencies into ART boards during PI planning? Nooga Scale allows external dependencies to be tracked via board configuration. When adding teams or dependencies from other projects, use the workspace options “Team from another project” or “Dependent team,” and select the appropriate board layout. Note there are layout restrictions when mixing teams from several projects .
WSJF (Weighted Shortest Job First) queries/settings disappear or are visible to all users—what's happening? WSJF settings and queries are sometimes shared with all users and may be editable or deletable by anyone in the workspace. Save copies as needed, and communicate with your admins to manage shared configuration .
Why does the AreaPath default to root in some risk features and not to the train’s path? Certain features may default to the AreaPath root rather than the expected subpath for a train or team, which can impact visibility in boards and aggregated views. It’s advisable to review root vs. train area assignment for these items when configuring your boards .
What can I do if I'm having trouble with WIT definition files or scripts for advanced configuration? Errors in executing configuration scripts, such as PowerShell files for WIT definitions, generally mean there is an issue with script parameters or prerequisites. Double-check the instructions provided by Nooga Scale and reach out to support with the specific error for step-by-step troubleshooting .
Board layout issues: Adding teams from other projects changes board behavior or restricts layouts—how do I resolve this? If the board behaves differently or restricts certain layouts when you add external or dependent teams, review the limitations of workspace layouts in Nooga Scale. Sometimes, certain layouts are only available for single-organization or single-project scenarios; mixing teams can limit options .