#5637 - composr_homesite_support_credits: Consider better or alternate Mantis integrations
-
By PDStig
- Added
- 6 views
| Identifier | #5637 |
|---|---|
| Issue type | Feature request or suggestion |
| Title | composr_homesite_support_credits: Consider better or alternate Mantis integrations |
| Status | Closed (rejected) |
| Tags |
Roadmap: Over the horizon (custom) |
| Handling member | Deleted |
| Addon | General / Uncategorised |
| Description | Mantis is a good bug tracker, but it is overwhelming and not very intuitive. I've frequently had to look up on forums to understand what database values match certain labels in the system. And there's no easy way to create a quick URL to auto-apply certain filters to the issue view page. The mobile view is also broken and has no way to change the project.
I propose for v11 we move back to the way we did things with ocPortal: use our own simplified in-house issue tracker via an addon / modules / etc. Or, at the very least, consider these proposals and integrate them with Mantis, leaving the Mantis interface out of the equation for most users. Here are some key features I am thinking: * Use the simplified interface / wizard I recently made in v10 for reporting issues. * Create a module for displaying issues. On browse, have a results table for displaying issues (be sure to display issue ID, label, project / category, status, last updated, # comments, and maybe rating). Use the new filtering capabilities (e.g. points ledger) for filtering. On view, have a field-map screen, and a rating / comments section. Comments are tied to website comments forum. * Also have a new profile tab which displays the issues a member reported and also handled / resolved. * Add new privileges pertaining to the issue tracker, such as who can resolve / close issues, who can edit the original details, and so on. * Use the revisions system for tracking changes to an issue. * Add notification types for issues. Also make sure members can monitor issues. * Issues should be resource meta aware so they can be managed through Commandr / WebDAV especially to mass-move etc. Issues should follow a category -> entry pipeline where the category is the "project" and the entry is the issue. * For feature requests, add the ability to escrow points onto an issue. Other members in the community can escrow as many points as they wish onto a feature request to "sponsor" it. When an issue is resolved, the reporter gets a percentage of the total escrowed points (let's say 30%) and the resolver gets the rest (let's say 70%). If an issue is closed with no resolution, all escrowed points are refunded. * On top of escrowed points, reporters and resolvers should also receive a small base number of points per resolved issue. This applies to all issue types, not just feature requests. |
| Steps to reproduce | |
| Additional information | As Composr moves to a Bazaar model and becomes more of a social / community project, I feel these changes will further follow with that vision. It will also add an additional use for points. |
| Related to | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".
Comments