Roadmap
Last Modified: August 21, 2003 08:08AM
|
|
(Any)
|
Description
0.18.0
- XHTML compliance.
- Bug history logging
- Basic support for custom fields.
- Caching for query results within the same page
- Add admin subdirectory for admin scripts.
- Monitor bug (for anyone) - users can click a 'Monitor Bug' option to let them be included in the email notifications
- CSS Style Editor to be used to customise Mantis look'n'feel.
- Almost a complete re-write of code
- Focus on security
0.19.0
- Use Smarty templates at least for simple/advanced/print pages.
- More custom fields features
- Support diff emails which highlights the changes in the bug that caused the notification.
- Send an email per user including the information that the user have access to see + in the user's language. For example, in case of private bugnotes, one user may get them and the other may not.
- Bug relationship fields (Duplicate of, Depends on, Parent of, etc.)
- List modified files for each release - let users know what exactly has changed in each upgrade
- Little glyphs and graphics for site - asthetic niceties
- Bug Search (Advanced) - fleshed out search with multiple options (search in bugnotes, categories, etc)
1.x.x
- Mantis Logo - about time, right?
- Use Smarty templates for all pages
- Database abstraction layer - allow for Postgres, MS, and more
- Abstract account management - make it easier to integrate Mantis with other packages like PostNuke, PHPNuke, phpWebsite, ...etc.
- Have user settings per project - email preferences should be configurable on a per project basis
2.x.x
- Daily/Weekly report generation - generate a complex summary of the past day/week/month/year either on demand or via a cronjob or scheduled task.
- Move towards more complete (XHTML)HTML4/CSS conformance - except for form handling which requires nonstandard formatting
- PDF report generation - same as report generation expect into PDF format
- Nice bar and line graph charts (phplot/jpgraph) - generate plots based on the stats
- IP Tracking / banning - prevent spamming or harrassment from users
- Security Audit - examine every line, form, cookies, passwords, authetication for security weaknesses
- String/form handling Audit - make sure illegal and unsafe input is not allowed
- Interfaces for custom configuration
- Allow users to specify required fields
- Allow user to create own required fields
- Move some global settings into the database (?) - potential performance hit; advantage is simpler upgrading.
- "I forgot my password" email (requires different password storage system)
- plaintext, one-way crypt, de/encrypt, and no password authentication modes
3.x.x
Unassigned
- Show number of concurrent users - like Freshmeat.net
- Eliminate strtotime()
- Complex user profiles
- Moderation queue (?)
- User definable display fields (view all bugs page)
- Email module
- NNTP Mirroring (with threading)
- Sort view bugs by any field
- Auto update config file
- Auto show differences in config file when upgrading
- ETA support
- Priority support
- Projection support
- Move configuration variables into the database
- Multiple sort keys (?) - let people select more than one ordering for searches (complicated interface)
|
User Contributed Notes
Roadmap |
|
m@mullenweg.com
19-May-2004 2:17 |
#137
|
Why stop using strtotime()?
[Victor] I didn't personally add this one, but I think because strtotime() assumes a certain format for the time which is not the one used by all DBMSes. Hence, since Mantis now uses ADOdb, it should use its provided function to do such conversion. |
|
tk2.c.., will
03-Jul-2004 9:34 |
#164
|
[Victor] Is there a Mantis instance where we can see this in action? The best place to discuss this is on mantisbt-dev@lists.sourceforge.net. Also if you have the patch for this, please submit an issue on http://bugs.mantisbt.org and attach the patch (and preferrably added + modified files to the issue).
---
I implemented a fairly simple interface for multiple sort keys: Make the key a list of keys. Then sort first by the last key chosen, second by the next-to-last key chosen, ..., last by the first key chosen. If a key is already in the list, it is moved to the end of the list. I also include the direction in the key list.
The user chooses keys by clicking on the column names. Actually, I used up and down arrows after the column name, so the user could choose the column and sort-direction in one click.
Example:
Instead of making your column header cells link to "?sort=col1&dir=desc" and "?sort=col2&dir=desc", if the output is already sorted, say by column 3 descending, then the links become "?sort=-col3,-col1", "?sort=-col3,+col1", "?sort=-col3,-col2", "?sort=-col3,+col2", and "?sort=+col3". Since the last sort key was -col3, I would omit the link to sort by that myself, but including it should work fine.
If the user subsequently clicks on "?sort=-col3,+col2", then the sort links would be thus: "?sort=-col3,+col2,-col1", "?sort=-col3,+col2,+col1", "?sort=-col3,-col2", "?sort=-col3,+col2" (optional), "?sort=+col2,-col3", and "?sort=+col2,+col3". Note how col2 and col3 are not repeated, but are moved to the end of the key list. |
|
moudsen@allshare.nl
03-Dec-2004 10:07 |
#279
|
| Consider using LDAP authentication, based on a given LDAP group membership to allow easy administration |
|
|
|
| Last updated: Tue, 14 Oct 2008 - 9:34:22 |
|
|
