[RFE] Analysis history

[rromannissen]

What is the problem?

There is no way in Konveyor to browse analysis history to check the evolution of a given application.

Why is this a problem?

We have received feedback from multiple organizations and practitioners on the field about the need to keep track of the evolution of applications as changes are applied by migration teams. Knowing how the associated story points or incidents of an application evolve over time provides a measure of progress that can be consumed individually by application owners and migration teams or aggregated across the entire portfolio for potential senior management roles that might want to have an overview of the overall migration initiative.

Proposed solution

Even though storing all the information associated to issues for each analysis wouldn't be practical and would introduce very high storage requirements, Konveyor should at least store the following data for each analysis:

• Application
• Date
• Sources
• Targets
• Total story points
• Total number of incidents
• Number of incidents per category
• Version of the analyzed application if it can be determined (this could be difficult to obtain in binaries, but should be trivial when dealing with source code that uses proper build and dependency management tools.

This information should be made consumable at the application profile via graphs that display the number of incidents or story points over time, allowing the user to choose between the two previous metrics and determine the target period of time (Last 6 months, Last 30 days, Last 7 Days, Last 24 hours...). The user should be able to click on each point in the graph and get information on all of the above fields for the given analysis.

It would be desirable to have additional graphs under the Reports option in the left menu to consume this information in an aggregated way across the entire portfolio, although this could be fleshed out in a different RFE.

[rromannissen]

@jortel @JustinXHale please review and provide feedback!

[JustinXHale]

[jortel]

Let's flesh-out the application version requirement a bit more. I would assume that when modernizing applications users will start with the current version. They will create a branch and iterate on that. So, the version of the application will not likely change with each iteration. Unless, the version here is a commit (hash).

@rromannissen can you elaborate?

[shawn-hurley]

I might have a silly question here, but if the org does want to keep all of that information and subsequently take on the cost of storage, why wouldn't we let them?