The Problem
One of the challenges that I encountered this week was the need to include Advanced Roadmaps plans in a Jira DC to Cloud migration. As you may be aware, JCMA gives you the option to either migrate ALL plans, or none of them. There is no facility for selectively adding plans. This is a problem because the client instance has 1200 Roadmaps plans, and trying to add that many plans to a migration causes JCMA to crash.
I set out this week to build the foundations of what I’m calling the Roadmaps Insight Tool. The first version was intended to simply list every Roadmaps plan in an instance, and list each of its data sources (project, board, or filter).
The resulting dataset is useful in a number of ways. First, it gives transparency to a part of Jira that is otherwise quite opaque.
Second, it indicates which data sources on each plan are invalid; typically this is because the referenced data source no longer exists. A Jira administrator wanting to do a cleanup of the Roadmaps Plans could easily base that cleanup on this information.
Third, in the case of this particular client it allows us to