I confirm that I have searched the issue tracker
Before opening an issue, take a few minutes to search the issue tracker (both open and closed issues) for the feature you are requesting. This will reduce the need for issue triage and save time.
- I confirm that I have searched the issue tracker
Describe the feature
GitNex should jump to the comment that triggered a notification when clicking on said notification.
Additional context
Currently in Forgejo, if you click on a notification originating from a new comment (or new comments) in an issue or pull request, it'll jump to the specific new comment, or the first of the new comments if there's multiple. GitNex, on the other hand, jumps to the issue / pull request body, requiring you to scroll down to the new comment(s) and not providing any indication of what is the new comment(s).
Declaration
- I have carefully read and agree to follow the contribution guidelines.
### I confirm that I have searched the issue tracker
Before opening an issue, take a few minutes to search the issue tracker (both open and closed issues) for the feature you are requesting. This will reduce the need for issue triage and save time.
- [x] I confirm that I have searched the issue tracker
### Describe the feature
GitNex should jump to the comment that triggered a notification when clicking on said notification.
### Additional context
Currently in Forgejo, if you click on a notification originating from a new comment (or new comments) in an issue or pull request, it'll jump to the specific new comment, or the first of the new comments if there's multiple. GitNex, on the other hand, jumps to the issue / pull request body, requiring you to scroll down to the new comment(s) and not providing any indication of what is the new comment(s).
### Declaration
- [x] I have carefully read and agree to follow the [contribution guidelines](https://codeberg.org/gitnex/GitNex/wiki/Contributing).