Given the amount of time this idea has been open and given that it has not passed the required vote threshold to be considered for roadmap (current vote count is currently 9), I'm going to mark this idea as Not Planned. If the votes for this idea increase drastically we can revisit this, or alternatively if any other ideas for the same enhancement exist then votes from this idea can be merged into the alternate.
I think it's beyond ridiculous that such a vital part of the object is completely ignored by the comparison tool. This (along with the other things inexplicably ignored, such as stage logging and exception messages) adds a huge amount of risk to the deployment process.
Seriously, it shouldn't even need to be raised here for it to be on the to-do list!
This enhancement is particularly needed because, it can lead to confusion and inefficiencies, especially in collaborative environments. Having the capability to compare the application modeller would significantly improve our ability to track changes.
I understand that the idea has not yet reached the required vote threshold to be considered for the roadmap, but I believe it deserves further attention.
Agreed with the above commenters. It's kind of ridiculous that something like that needs to be up to a vote. Compare should compare, and any differences should be pointed out. Anything else is half baked, no?
Absolutely true. It's been pointed out several times that ideas shouldn't be judged solely on vote counts. This is yet another example of a strong idea being overlooked simply because of the numbers. I truly hope the BP team recognizes this now—it's high time for a change!
A red flag for sure.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
