search

CATcher-org / CATcher

CATcher is a software application used for peer-testing of software projects.
https://catcher-org.github.io/CATcher/
MIT License
71 stars 66 forks source link

Unable to unlink issue for the tester after the issue is marked as duplicate by the dev team #1231

Closed AlagappanRa closed 7 months ago

AlagappanRa commented 7 months ago

Describe the bug Lets say during phase 2 of the triaging, the dev team marks issues 5 and 6 as duplicates of issue 4. This means, Issue 4 is the "main issue" and 5 and 6 are the "duplicated" or "linked issues".

Say only issue 4 is written by me. In phase 3, upon arriving at https://catcher-org.github.io/CATcher/phaseTesterResponse, I am unable to edit/appeal to "unlink" issues 5 and 6 away from my issue, issue 4.

To Reproduce My issue, equivalent to issue 4 in the example above. image

The two other issues marked as duplicates by the dev team, this would be equivalent to issues 5 and 6. image

What I see on my Catcher Page. I am not allowed to appeal or respond. image

Expected behavior This should not be the case as whether the dev team classifies the tester's issue as the main issue or not should not affect whether or not the tester is able to respond. The tester should be allowed to appeal to unlink if that is the appropriate course of action.

Additional context High severity.

damithc commented 7 months ago

That's a fair point @AlagappanRa For now, we only ask the consent of the testers who reported the 'duplicates'. Asking the tester of the 'original' would effectively double the number of such checks done by students, and also significantly increase the disputes we have to process. Given testers are not affected that much from their bugs being flagged as duplicates, I think this is a reasonable tradeoff.