Hey there! @Daniel Peñalba
Thank you for your reply. Let me answer your questions... These metrics are definitely valuable in my daily process. As a game developer, it is not uncommon to deal with large sums of assets that must be checked-in (especially with refactoring or organization). And thus, it is not uncommon to have my Pending Changes tab have its list of total items changed extend below the fold of the application window.
The reason that this metric was useful was for sanity checks prior to check-in. Let's say that I'm checking in a large sum of assets that are "Changed," and I do not want to include any "Moved" or "Added" assets. In this situation, I would have to scroll below the fold and verify that each category (should it exist) is marked 0 out of X. With the previous version, I could verify that my numbers lined up just by staring at the header.
Additionally, it is also useful to have a clean summary of how large your changeset will be, prior to check-in. Because perhaps it might be trying to do too much in one check-in
I hope that this makes sense, and I will gladly clarify further if it does not. If you are willing to add this feature back to the alpha version and put it on your roadmap somewhere, that would make me VERY happy! 😃
Hey there! @Daniel Peñalba Thank you for your reply. Let me answer your questions... These metrics are definitely valuable in my daily process. As a game developer, it is not uncommon to deal with large sums of assets that must be checked-in (especially with refactoring or organization). And thus, it is not uncommon to have my Pending Changes tab have its list of total items changed extend below the fold of the application window. The reason that this metric was useful was for sanity checks prior to check-in. Let's say that I'm checking in a large sum of assets that are "Changed," and I do not want to include any "Moved" or "Added" assets. In this situation, I would have to scroll below the fold and verify that each category (should it exist) is marked 0 out of X. With the previous version, I could verify that my numbers lined up just by staring at the header. Additionally, it is also useful to have a clean summary of how large your changeset will be, prior to check-in. Because perhaps it might be trying to do too much in one check-in I hope that this makes sense, and I will gladly clarify further if it does not. If you are willing to add this feature back to the alpha version and put it on your roadmap somewhere, that would make me VERY happy! 😃
