I am familiar with the show "Only relevant" option but I am hoping there is a way to designate particular CSs as relevant (or "Key" in the image below). I recently changed my philosophy on check-ins. This resulted in having more changes set as I want to minimize working on more than one bug/feature/improvement in one change set. However, the number of change sets could be less desirable for a code reviewer as many change sets may all be working towards a train of though (I am thinking: one Jira "story" can be thought of as many "tasks"). The biggest problem I see is that there is likely underdeveloped implementations as I am addressing a "task". I still want to get the isolation for the case when another person wants to look at smaller changes made for a subtask if they want a bit more clarification on what would otherwise be a much harder change set to follow.
I hope that make sense. I would hope that when I select the "Only relevant" or some other existing functionality would generate the BranchCondensedToKeyCSs image below from the Current branch. I would also be interested in how to permanently condense two changeset (say: when I forget to include a newly added file or forgetting to save a last minute change, etc)
Currently 50 versions behind but that is out of my control as I am not the admin.
Thanks