issuetracker:specs
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
issuetracker:specs [2008/05/27 08:34] – VCS integration cweiske | issuetracker:specs [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 2: | Line 2: | ||
Here you can find the list of requests for features to be added to the bug tracker, this will in time be split into implemented, | Here you can find the list of requests for features to be added to the bug tracker, this will in time be split into implemented, | ||
- | |||
- | |||
- | |||
- | |||
- | |||
==== Main Requirements ==== | ==== Main Requirements ==== | ||
Line 19: | Line 14: | ||
* History, changed who/when, the bug report itself and relevant files/ | * History, changed who/when, the bug report itself and relevant files/ | ||
* Multiple category bugs (ex. documentation and streams) each with own status | * Multiple category bugs (ex. documentation and streams) each with own status | ||
+ | * Multiple typed bugs (ex. a feature request for the streams extension) | ||
* Ability to hide email address (obfuscated or otherwise) from public view | * Ability to hide email address (obfuscated or otherwise) from public view | ||
* RSS Feed and Email Subscription | * RSS Feed and Email Subscription | ||
* When a bug is reclassified, | * When a bug is reclassified, | ||
* Bug Categories by extension, and/or tags for notification (email) purposes, (e.g. I want to be notified of new bugs in the PCRE extension) | * Bug Categories by extension, and/or tags for notification (email) purposes, (e.g. I want to be notified of new bugs in the PCRE extension) | ||
- | |||
- | |||
- | |||
==== Secondary Requirements ==== | ==== Secondary Requirements ==== | ||
Line 33: | Line 26: | ||
* Data push to IRC | * Data push to IRC | ||
* No captcha for people logged in with @php.net | * No captcha for people logged in with @php.net | ||
+ | * No captcha for people who confirmed (via email) their account | ||
* Preview bug report (before submit) option | * Preview bug report (before submit) option | ||
* Ability to save searches to make quick searches + More organized search page | * Ability to save searches to make quick searches + More organized search page | ||
Line 38: | Line 32: | ||
* VCS (Versioning Control System, e.g. CVS and SVN) integration | * VCS (Versioning Control System, e.g. CVS and SVN) integration | ||
* Script to push commit message into bugtracker which gets appended as comment to bug | * Script to push commit message into bugtracker which gets appended as comment to bug | ||
- | * Linking to SVN revision | + | * Linking to SVN & CVS revision |
+ | * Link from VC to bugtracker (see trac) | ||
+ | * Allow users to vote on bugs | ||
+ | * Pluggable user authentication | ||
+ | * REST-interface to extract information from the bugtracker (e.g. to package homepage, IRC) | ||
+ | * Be able to see CVS commits regrading a bug report based on an special ID in the commit log message |
issuetracker/specs.1211877256.txt.gz · Last modified: 2017/09/22 13:28 (external edit)