Customizing Agile 2.0 Performance Analytics Dashboard

[udaykumarko]

Hi All,

I have installed the Performance Analytics Content Pack for Agile 2.0 plugin, which created the following default dashboards:

• Agile 2.0 EPIC Dashboard
• Agile 2.0 Prior Release Dashboard
• Agile 2.0 Sprint Release Dashboard
• Agile 2.0 Release Dashboard
• Agile 2.0 Sprint Dashboard
• Agile 2.0 Team Dashboard

I need to build a custom Agile Metrics dashboard for my team and would like to reuse the existing OOB dashboards/widgets instead of creating everything from scratch.

I have a few questions:

• Should I clone one of the existing dashboards and customize it?
• Which OOB dashboard is the best starting point?
• Can the existing widgets/indicators be reused for custom requirements?
• Where can I view the underlying Performance Analytics indicators/widgets (or reports, if applicable) used by each of these OOB dashboards?

Any suggestions or best practices would be appreciated.

Thanks!

[Vikram Reddy]

Hi @udaykumarko,

Yes, clone one of the OOB dashboards rather than starting from a blank canvas, that's the supported path here. One thing worth calling out first though: in your screenshot every Agile 2.0 dashboard in the picker shows a "- Old (Inactive)" suffix. That's not something broken on your instance, it's a known marker ServiceNow appends when it pushes legacy Performance Analytics content toward the newer Platform Analytics experience, there's a support KB specifically titled around Agile dashboards picking up that suffix after a platform upgrade. So before you pick a starting point, check whether your instance has since re-registered active, non-suffixed versions of these same six dashboards under the "Agile 2.0" group. If it hasn't (which is common, the content pack itself hasn't been rebuilt natively on Platform Analytics), the "old" ones are still perfectly valid, live data, they're just flagged inactive in the picker, not deleted.

With that out of the way, here's how I'd approach the rest of it:

1. Pick the OOB dashboard whose grain matches your audience: the Team Dashboard for velocity/throughput rollups management cares about, the Sprint Dashboard for day-to-day burndown and scope-change tracking, or Release/Epic if your metric is longer-horizon. There isn't one universal "best" starting point, it depends on which grain your custom metrics live at.
2. Use the Duplicate action on that dashboard (available from the dashboard's menu) rather than the "Copy Widget" option on individual widgets. Duplicate carries over the tab structure and the widget-to-indicator wiring intact, whereas a straight widget copy is documented to drop the attached indicators, you'd have to re-add each one by hand. So clone at the dashboard level, then add/remove tabs and widgets inside the copy.
3. Indicators and widgets are shared, reusable records, an Indicator isn't "consumed" by one dashboard. On your custom dashboard you can add a brand-new widget and point it at any existing OOB indicator (Burndown, Velocity, Cycle Time, etc.) without touching the original dashboard at all.
4. To see exactly which indicator and breakdown feed a given widget, open the dashboard in edit mode, click into the widget's configuration/gear icon, it shows the source Indicator directly. For the full inventory, go to the Performance Analytics application menu and open Indicators, then filter by the source table the Agile 2.0 pack reports off (rm_story, rm_scrum_release, and related Agile 2.0 tables). That list is your map of everything the six OOB dashboards draw from.

One more thing: It's worth checking /now/platform-analytics-workspace/migration-center on your instance, that's where ServiceNow is staging the move of legacy PA content (including packs like this one) into Platform Analytics, and it'll tell you if Agile 2.0 has migration status tracked yet.

Thank you,
Vikram Karety
Octigo Solutions INC

[fknell]

Hi @udaykumarko,

The Agile Development 2.0 module was declared as deprecated with the Australia Release and will be phased out over time. The latest with the end of your current subscription cycle, you will lose support and no fixes will be provided anymore.

Hence, I would not build any new functionality based on it, and I guess this is why after a fresh installation, all dashboards are marked as old/inactive.

Hope this helps!