Skip to content
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

Consider issue version on issue filters #739

Open
Tracked by #781
MarceloRobert opened this issue Jan 9, 2025 · 0 comments · May be fixed by #862
Open
Tracked by #781

Consider issue version on issue filters #739

MarceloRobert opened this issue Jan 9, 2025 · 0 comments · May be fixed by #862
Assignees

Comments

@MarceloRobert
Copy link
Collaborator

Currently the issue filter on treeDetails or hardwareDetails is only considering the issue_id, which is only part of the primary key. In case there are 2 issues with the same id but different versions, the filter will currently catch both of them when it should catch only the one with the same version as the version of the selected issue for the filter.

@MarceloRobert MarceloRobert self-assigned this Jan 20, 2025
@Francisco2002 Francisco2002 mentioned this issue Jan 20, 2025
27 tasks
@Francisco2002 Francisco2002 moved this from Todo to In Progress in KernelCI Web Dashboard Jan 28, 2025
Francisco2002 added a commit that referenced this issue Jan 30, 2025
- use tuple (issue_id, issue_version) shape to pass issue filters
- create function to format issue name with version

Part of #739
Francisco2002 added a commit that referenced this issue Jan 30, 2025
- create a function to validate issue id and issue version for a issue
- pass issue versino in functions to validate build/test (tree and
  hardware)
- use formatter function to issue label
- send the issue version in frontend

Close #739
@Francisco2002 Francisco2002 linked a pull request Jan 30, 2025 that will close this issue
@Francisco2002 Francisco2002 moved this from In Progress to In Review in KernelCI Web Dashboard Jan 30, 2025
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- use tuple (issue_id, issue_version) shape to pass issue filters
- create function to format issue name with version

Part of #739
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- create a function to validate issue id and issue version for a issue
- pass issue versino in functions to validate build/test (tree and
  hardware)
- use formatter function to issue label
- send the issue version in frontend

Close #739
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- use tuple (issue_id, issue_version) shape to pass issue filters
- create function to format issue name with version

Part of #739
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- create a function to validate issue id and issue version for a issue
- pass issue versino in functions to validate build/test (tree and hardware)
- use formatter function to issue label
- send the issue version in frontend

Close #739
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- create a function to validate issue id and issue version for a issue
- pass issue versino in functions to validate build/test (tree and hardware)
- use formatter function to issue label
- send the issue version in frontend

Close #739
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- create a function to validate issue id and issue version for a issue
- pass issue versino in functions to validate build/test (tree and hardware)
- use formatter function to issue label
- send the issue version in frontend

Close #739
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- use tuple (issue_id, issue_version) shape to pass issue filters
- create function to format issue name with version

Part of #739
Francisco2002 added a commit that referenced this issue Jan 31, 2025
- create a function to validate issue id and issue version for a issue
- pass issue versino in functions to validate build/test (tree and hardware)
- use formatter function to issue label
- send the issue version in frontend

Close #739
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Review
Development

Successfully merging a pull request may close this issue.

2 participants