Modify ↓
      
Opened 13 years ago
Last modified 2 years ago
#10763 new defect
fix changeset search results
| Reported by: | Christian Boos | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | next-stable-1.6.x | 
| Component: | version control | Version: | 1.0dev | 
| Severity: | minor | Keywords: | search | 
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
I just noticed the following glitch:
- the changeset results displayed show something like 
[134]: blah, without any hint about the repository; this should rather be[134/reponame]or[134] in repo1, repo2, the same kind of consolidation that we (should) get in the timeline 
(should, as that's also broken)
Attachments (0)
Change History (4)
comment:1 by , 10 years ago
| Owner: | removed | 
|---|
comment:2 by , 9 years ago
| Milestone: | next-stable-1.0.x → next-stable-1.2.x | 
|---|
comment:3 by , 5 years ago
| Milestone: | next-stable-1.2.x → next-stable-1.4.x | 
|---|
  Note:
 See   TracTickets
 for help on using tickets.
    


  
Moved ticket assigned to next-stable-1.0.x since maintenance of 1.0.x is coming to a close. Please move the ticket back if it's critical to fix on 1.0.x.