-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
navigate over unresolved issues #7443
Comments
@bsekachev @nmanovic can you assign please me this issue? |
@ArMaxik can you please help me recreate the issue? |
@tahamukhtar20 Glad to hear you are working on this issue!
There is a perfect button "show/hide resolved issues", but buttons "find the next/previous frame with issues" ignore it |
@nmanovic @bsekachevv is the issue still open, if so can you please assign it to me |
@thekavikumar , the issue was already assigned. @tahamukhtar20 , could you please confirm that you are working on it? |
@nmanovic you can unassign. I am not able to work on this currently. Thanks |
@thekavikumar , please let me know if you want to take the issue. |
@nmanovic yeah, I will take the issue |
This reverts commit 07142de.
) Resolved issue #7443 It skips the frames where all issues have been resolved! ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch - [x] I have created a changelog fragment <!-- see top comment in CHANGELOG.md --> - [x] I have updated the documentation accordingly - [x] I have added tests to cover my changes - [x] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword)) - [x] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning)) ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern.
Resolved in #7653 |
Actions before raising this issue
Is your feature request related to a problem? Please describe.
There are a some resolved issues in the job. I've gone through the annotations and added some new issues. Now annotator to fix them should somehow find all frames with unresolved issues.
In the latest version of cvat (2.10.2) this is impossible. There is only a way to navigate over frames with issues (both resolved and unresolved):
If there are a lot of resolved issues, it's hard and annoying to find frames with new issues.
Describe the solution you'd like
Cheking show/hide resolved issue should also hide frames with them:
This will allow you to skip frames with unresolved issues.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: