Affects Version/s: 0.11, 0.12.0
Fix Version/s: 0.12.0
So this one took a while to isolate, but is pretty crazy.
If you take a look at that code snippet, that is pretty nuts! Since the 2 fields come from the same original table, renaming one causes issues with both. WUT. The even weirder part is not that they both get renamed, but that they both become the unrenamed value.
Interestingly, flipping the value of the projection changes the order of the output, so it looks like it's whatever the final reference is. ie
This seems to imply the solution: make copies of the Schema. I added a test and will hopefully have a patch soon.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|5d 4m||1||Jonathan Coveney||18/Dec/12 00:19|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Duplicate [ 3 ]|