9
4
At my place of work, it has been decided to move many processes to Sharepoint. I'm now looking into how Sharepoint can be used for bug tracking (à la Mantis, FogBugz etc. but within Sharepoint). Specifically, we're using a collaboration room and the solution must work inside that.
I know that I can create lists using an "Issue tracker" template, but it lacks workflow, integrated correspondence (like FogBugz), and audit log (any user can edit any field any time, without it being noted anywhere).
That's not sufficient, so I am looking for "bigger" solutions but haven't yet found anything at all.
This question is similar but aims at Helpdesk use; we aim at bug tracking and change requests to a system.
I'm open to suggestions! As I'm not an administrator, I can't just grab a Sharepoint component and install it for testing. I'm looking for experiences, documentation, white papers, screen shots -- the actual downloadable will be relevant later.
Ideally, some of these matters should be covered:
- Support for different ticket types (bug, feature, inquiry, internal task).
- Configurable workflow per ticket type, no fixed number of steps.
- Configurable read/write permissions per field and per workflow status.
- Configurable dashboard for managers with nice charts.
- Configurable email notifications.
- Correspondence à la FogBugz. (Challenge: we use Notes, not Exchange.)
The best advice? Stay far, far away from Sharepoint. Its SQL is bastardized, file uploads are an absolute pain, and the real goal seems to be pushing everyone back to using Office. The Discussions section is a joke, and wants to integrate heavily into Outlook instead of being by itself.
Using Sharepoint as anything but a place to keep a few policy docs is a bad idea. Right now I'm trying to create a SP Wiki (it too has been deemed) and I'm resorting to coding everything in HTML (inlined with CSS, no wiki template support).
It may be possible, but you will fight it more than you will use it. – Steiv – 2010-01-21T14:30:50.753
Yes, it seems evident that SP exists to keep the MS Office cash-cow alive against the Web 2.0 battlefront. I would also have avoided SP, given the choice, but it's been decided from above and I'm going to make the best of it. -- I am pleasantly surprised that the collaboration room does have several useful features, and editing uploaded (Office) documents is straightforward (they're saved, reuploaded, and versioned, all in one automatic step). Too bad it only works for Office documents! To the point: the "issue tracker" and "workflow" features are far from useful for the above purpose! – Torben Gundtofte-Bruun – 2010-01-21T16:51:26.953
I think you're seeing what I'm seeing with SP- anything dealing with the core of Office works, everything else is hacked together. What we've done at our office is just integrate the RSS feeds of Jira (our issue tracking software) with SP to get an update list in SP, but use Jira instead for the tracking. As a bonus, Jira supports Wiki syntax, so editing and commenting is a breeze. – Steiv – 2010-01-21T18:28:04.173
You should ask at http://softwarerecs.stackexchange.com
– Nicolas Raoul – 2016-02-29T04:15:34.167