33 | | Since the tracker has no !CodeTags component I will put that here: |
34 | | * Feature "upgrade CodeTag to issue". Click on one of the CodeTags to be brought to a "New Ticket" page, with fields already completed (will require some parsing). Bonus points if the CodeTag (and surrounding comments, which might be numerous) can optionally be removed from the SVN and a commit log entry automatically generated. |
35 | | * Having a huge code base makes the table with the tags so huge that even modern browsers can hardly display it. Maybe: |
36 | | * Split it up into multiple pages |
37 | | * Choose display for only specified tags |
38 | | * Chose display for only specified path in repository |
39 | | * Allowing regex's for the [code-tags] fields would increase flexibility (scan_files, scan_folders, tags). |
| 28 | * Feature "upgrade CodeTag to issue". Click on one of the CodeTags to be brought to a "New Ticket" page, with fields already completed (will require some parsing). Bonus points if the CodeTag (and surrounding comments, which might be numerous) can optionally be removed from the SVN and a commit log entry automatically generated. |
| 29 | * Having a huge code base makes the table with the tags so huge that even modern browsers can hardly display it. Maybe: |
| 30 | * Split it up into multiple pages |
| 31 | * Choose display for only specified tags |
| 32 | * Chose display for only specified path in repository |
| 33 | * Allowing regex's for the [code-tags] fields would increase flexibility (scan_files, scan_folders, tags). |