开发者

Sharepoint bug database - any good? [closed]

Closed. This question is opinion-based. It is not currently accepting answers. 开发者_Go百科

Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.

Closed 3 years ago.

Improve this question

We've been using Sharepoint as a poor man's bug tracking database for the last couple of projects that we did. No one is really happy with the solution so I'm looking for alternatives. I happened to stumble upon the Bug Database Template for Sharepoint. If it is halfway decent it might be a good choice for us since the transition would be smooth as the team is already used to Sharepoint.

Anyone have any experience using this template? Any major problems? Any major missing features? Is there any documentation out there beyond that download page?

Thanks for the help.


I can't speak on the Bug database itself but our users have had shown some very positive acceptance of some of the other "Fab 40" SharePoint templates (Multiple Project Budgeting, Knowledge Base, etc.)

Your best bet is to just create a pilot site using the template and have a few of your people check it out.


Stop struggling against the tide, bite the bullet and get TFS - or something similar. :-)

Given the historic challenges of using Sharepoint for workflow, and its (in)ability to effectively organize, manage, report, and summarize information - you're unlikely to see a dramatic step forward with the bug template. You may find some things a bit easier, but for the most part, I expect you will continue to be unhappy with Sharepoint as a bug management tool.


TFS 2012 does not have bug tracking in per se. It is managed as a work item. Unless I'm missing something


sorry forgot to include this with my answer based on my small research - https://softwareengineering.stackexchange.com/questions/206031/use-tfs-to-track-bugs-from-production-support

0

上一篇:

下一篇:

精彩评论

暂无评论...
验证码 换一张
取 消

最新问答

问答排行榜