[go: up one dir, main page]
Menu ▾ ▴

Search bugs: labels:"SVN"  Maximize  Restore

If you are developing code, even on a team of one, without an organized database listing all known bugs in the code, you are simply going to ship low quality code. On good software teams, not only is the bug database used universally, but people get into the habit of using the bug database to make their own "to-do" lists, they set their default page in their web browser to the list of bugs assigned to them, and they start wishing that they could assign bugs to the office manager to stock more Mountain Dew.

More in Painless Bug Tracking article by Joel Spolsky

 Help

Showing 7 results of 7

# Summary▾ Milestone▾ Status▾
  • Sort A -> Z
  • Sort Z -> A
  • Filter by Status
 Owner▾ Created▾ Updated▾ Labels▾ Priority▾ Votes▾
1036 SVN team project files disappear 5.4.2 closed-fixed Martin Fleurke 2021-02-12 2021-05-19 SVN, Team Project 9 0  
922 --mode=console-translate crashes on team project 4.1 closed-out-of-date 2018-09-10 2021-06-21 svn, console-translate 9 1  
881 svn_commit_segmentation.groovy script fails 4.1 closed-invalid 2017-09-19 2017-09-19 SVN 5 0  
836 Changes to segments get lost in team projects randomly and silently 4.1 closed-fixed Alex Buloichik 2016-09-08 2017-01-09 team projects, svn, 4.0 5 0  
790 project_save.tmx gets reverted to an older version in an SVN project 3.5 closed-wont-fix Didier Briel 2015-12-28 2016-01-12 svn 5 0  
717 Wrong timezone in team project 3.1 closed-invalid 2014-10-30 2014-10-30 svn, team, timezone 5 0  
616 Discard of glossary term added during svn synchronization None closed-out-of-date 2013-09-20 2017-02-07 svn glossary 5 0  
  • Ticket Number
  • Summary
  • Milestone
  • Status
  • Owner
  • Creator
  • Created
  • Updated
  • Labels
  • Priority
  • Votes
 
(applies to this page only)