It seems that this issue is functioning as expected. The "ColorBy" feature is applying Heatmap Settings and remembering them in a way that is intuitive to the user. After testing, I can confirm that this story is resolved because the two issues mentioned in this story have been addressed and are working as expected:

1. If I color tracks "A" and "B" with "Heatmap Setting 1", and then color tracks "B" and "C" with "Heatmap Setting 2", track "A" also gets "Heatmap Setting 2" applied when it should remain at "Heatmap Setting 1"

2. If I apply a heatmap setting to a track, and then select that track and another track and apply a different heatmap setting, the heatmap setting that gets remembered is not necessarily the one that is currently applied. Instead, it seems that the track's "individual heatmap setting" is always remembered, not the "group's heatmap setting"

Since this issue is resolved and there seem to be no side effects related to this change, it will now be closed.

I have rebased this and created a pull request, and reassigned to Dr. Loraine.

I am sorry I have deleted clone from laptop, @Ivory can you do this?
If you need me, I can do this after going home, I am currently in office.

Can you (Ivory or Devdatta?) re-base the pull request onto the latest master branch?

Thanks for the clarification!

I think this one commit just got lost in our process and we're trying to get it back into place now.
It's been reviewed by two of us, so I think we can move to the pull request. I'll see if Ann wants us to let Mason take at pass it just to be safe.