search

CATcher-org / CATcher

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

Possible new section for "Issues Flagged" in Issues during Dev Response Stage #1050

Open Echomo-Xinyu opened 1 year ago

Echomo-Xinyu commented 1 year ago

Is your feature request related to a problem? Please describe. During the Dev Response Stage, my team is unsure about several issues and would wish to flag them out for revision later even after we have written a response to them. But there is no separate panel to record these issues so we have to record the issue number by ourselves and look for it by navigating to the corresponding page in the issue lists, which is very tedious especially when the list of issues is very long and we have to navigate to a different page.

Describe the solution you'd like I hope that there can be a separate section called "Flagged issue" or "Issue Pinned" with similar style as "Issues Pending Response" so that the issues mentioned above can be highlighted and easily accessed. From my understanding, this can be easily done by introducing a new tag for "flagged" and do the filtering accordingly.

Describe alternatives you've considered We can also introduce a new field in the existing "Issues Pending Response" and "Issues Responded" section as a red flag similar to the outlook email system and have a filtering button at the side so that when clicking the button, only the issues flagged will be displayed in the list. But I feel this may make the current UI look even more crowded and therefore I view this as an alternative.

Additional context I believe the above need is real for many users of CATcher and the situation should be self-explanatory. Do ask me in the thread if there is any issue!

damithc commented 1 year ago

Good suggestion, @Echomo-Xinyu For the time being, you can use the 'mark as pending' feature to push an issue back into the pending table, without losing any changes you've done to it already. image

Echomo-Xinyu commented 1 year ago

Good suggestion, @Echomo-Xinyu For the time being, you can use the 'mark as pending' feature to push an issue back into the pending table, without losing any changes you've done to it already. image

Ahhh I see. Thank you for the clarification! I interpreted it as closing the issue and therefore never bothered to learn about its actual functionality. I think then in this case, would it better to change it to a flag so that its functionality can be clearer for users without prior knowledge?

image
kkangs0226 commented 1 year ago

As for the cross button, on hover it will show "Mark as pending", so users can be informed of the button's functionality. I think the flag icon may be misleading in this case, the "flagging/pinning" functionality can be introduced as a separate feature in CATcher.

vigneshsankariyer1234567890 commented 1 year ago

I think this is a very nice-to-have feature. Shall we proceed to work on it for the next version?

damithc commented 1 year ago

In the spirit of not adding CATcher features unless there is a strong need for it, I think using a more appropriate icon (both x and flag seems not quite right) seems like the way go go here.