So, more thoughts on this. One way to convey better what is going on, would be to visually group the bugtarget with the bug number. That way when you scan down the list, you will see the duplicate number, but related to a different project/task.
So, something like:
| #1234 - Firefox | Something wrong about something | Low | Confirmed | | #4234 - Thunderbird | Emails something something | Low | Confirmed | | #1234 - xul-runner | Something wrong about something | Low | Confirmed |
The visuals could vary, use a border and keep them as 2 cells, but that's the main idea.
So, more thoughts on this.
One way to convey better what is going on, would be to visually group the bugtarget with the bug number. That way when you scan down the list, you will see the duplicate number, but related to a different project/task.
So, something like:
| #1234 - Firefox | Something wrong about something | Low | Confirmed |
| #4234 - Thunderbird | Emails something something | Low | Confirmed |
| #1234 - xul-runner | Something wrong about something | Low | Confirmed |
The visuals could vary, use a border and keep them as 2 cells, but that's the main idea.