We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Currently, the migration effort can be measured visually in the webapp by using the colored elements from the viewer.
To get a measurable statistic, it would be useful to also have information available about the estimated effort.
I would like to see an effort in the range [0..10] where 0 is no effort and 10 is incredible.
[0..10]
0
no effort
10
incredible
This effort should exist on each individual message. From there, the result could be summed up to each element and again summed up to the whole file.
As alternative, the effort could only be appended to each element which would make identification harder.
No matter how deep the level of information, the effort will stick to message anyway.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Is your feature request related to a problem? Please describe.
Currently, the migration effort can be measured visually in the webapp by using the colored elements from the viewer.
To get a measurable statistic, it would be useful to also have information available about the estimated effort.
Describe the solution you'd like
I would like to see an effort in the range
[0..10]
where0
isno effort
and10
isincredible
.This effort should exist on each individual message. From there, the result could be summed up to each element and again summed up to the whole file.
Describe alternatives you've considered
As alternative, the effort could only be appended to each element which would make identification harder.
Additional context
No matter how deep the level of information, the effort will stick to message anyway.
The text was updated successfully, but these errors were encountered: