Thanks Aley for posting this because I am having the same concern with this.
Working nearly 1 year with TestRail, I have recently been poked by one of my people that he really finds difficult when working on a testcase without being aware of defects found on the testcase in question.
This mostly happens when we use Copy & Move feature. I understand why the results should not be copied as it doesn’t make any sense to use the result of last execution. I also observe that there is a field References in Testcase to refer to items such as requirement or bugs on external systems.
I think we should have the similar thing for internal referencing (only inside TestRail). Say like we should have:
1. list of testcases that having connection to this testcase (perfectly ones this copied from/to)
2. as the subject Aley stated, list of defects ever found on this testcase in this release and associated testcases in older release.
3. the list of defects should be editable so that we can focus on major bugs by removing minor ones.
Ideally this would look like this: we have testcase A as root, testcase B copied from A, testcase C copied from B; then any defects logged to A or B should be seen by C - the current one (it probably needs updating task triggered whenever we write down a bug).
The simple solution is to have a mapping table that allows user to add internal references to it however this would require lots of manual work done.
I can imagine the complexity when implementing this feature but this would add significant values to TestRail in the end.
Pop @ Unit4