You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Brief: A unique distinguishing attribute for each finding in the "Code-Review: Comment Explorer" for referencing to findings for e.g. bulk rework of review findings would enhance code review/rework aproaches.
Problem: So far the title and the description section of a finding are shown in the "Code-Review: Comment Explorer". Since both, the title and description can have multiple instances in the "Code-Review: Comment Explorer"- view, referencing to a particular finding is not simply feasible.
Suggested solution: An accending attribute in the "Code-Review: Comment Explorer"- view would be beneficial (like an index) which is not part of the code-review.csv could help referencing to particular findings in the "Code-Review: Comment Explorer"-view. This would not get in conflict with the findings id in the code-review.csv since it would be a feature of the view itself.
The text was updated successfully, but these errors were encountered:
🧩 Accending finding-index
Description
Brief: A unique distinguishing attribute for each finding in the "Code-Review: Comment Explorer" for referencing to findings for e.g. bulk rework of review findings would enhance code review/rework aproaches.
Problem: So far the title and the description section of a finding are shown in the "Code-Review: Comment Explorer". Since both, the title and description can have multiple instances in the "Code-Review: Comment Explorer"- view, referencing to a particular finding is not simply feasible.
Suggested solution: An accending attribute in the "Code-Review: Comment Explorer"- view would be beneficial (like an index) which is not part of the code-review.csv could help referencing to particular findings in the "Code-Review: Comment Explorer"-view. This would not get in conflict with the findings id in the code-review.csv since it would be a feature of the view itself.
The text was updated successfully, but these errors were encountered: