Our company uses HP Quality Center for managing/tracking defects and other types of issues.
I would like to have either a separate system or some integration with QC that will allow VOTING for issues by developers on my team.
Is this possible to do on QC? Is it an inherent feature of some other issue tracker?
Voting is possible in jira.
Voting on issues, bugs and the like is possible with Gemini.
Related
I am building a website for a client. He's asking me to do security audit of the website. I don't have expertise in security audits and the budget is low. However, I am trying to give the best value to my client. Is there any tool using which I can perform security audit of the website at a low cost?
There are also a few SaaS vulnerability scanning tools that I personally use for my website. Some are free or have subscription-based plans according to users' budgets. Providing you with a detailed report along with consultation from a security expert if required.
I have faced similar issues in the past, it's difficult to find an all in one solution as it is and usually the clients don't even know what they want, also they don't realize that getting security audits done will subsequently increase the cost from the original budget by a huge margin.
I did however, go through the comments and found https://reconwithme.com mentioned, will have a look and provide feed back after using it. I have tried acunetix and they're good but is extremely expensive for start ups who are just entering the game.
Forgot to mention the tool I use, its called ReconwithMe.
I have a small software project with a couple clients. What I'm looking for something with the following abilities:
clients can submit feature requests, bugs, or tasks
clients can see the status of open and closed issues
clients can see a change log
a place for me to post updates or news
Nice to haves:
clients can only see the issues that
they've posted; not other clients'
a hosted solution
So far, the choices seem overwhelming. I've looked at Mantis and Hiveminder. Unfuddle seems pretty close. I've avoided FogBugz for the price (and it seems like overkill) and Trac as I'm trying to avoid hosting something myself. Most of the existing solutions seem to be geared towards a team of developers and not for developer-client relations. Anyone have any recommendations?
I know that you said you'd rejected FogBugz -- but your description makes it sound like this might be a solo development effort. Have you considered the free Student and Startup Edition of Fogbugz?
I ended up going with Mantis. Its per project permissions actually works out pretty well for multiple exclusive clients.
Take a look at uservoice.com and getsatisfaction.com - probably what you need. It's not positioned as bug-tracking, so you won't have complex workflows or permission schemes, I guess, but maybe that's right for a small team.
Igor
My company is a custom development shop for a number of projects, some larger and some smaller. Currently we handle all of our client communication through email. So we email a design doc, they mark it up and send it back. Then we roll out a beta version of their product and they email us with any bugs, new features, etc. And so on....
As I am working on implementing a new bug tracking system (it looks like it will be Mantis right now), I got to wondering how we could best allow our customers an interface with our development process that would provide better tracking of feature requests and client submitted bugs as well as communicate our responses back to the client.
If anyone is aware of a a bug tracking system that does this exceptionally well I'd be interested to hear of that. Otherwise I'm just looking for some general guidelines or good business practices that have allowed your companies to interface effectively and efficiently with your clients.
UPDATE: My company uses a LAMPP stack and as we are a small shop with a limited budget we tend to stick to tools that are open-source and free.
Do most people either use Team Foundation Server to handle this or emails back and forth?
I think the key is to have the dedicated tracking system there for bugs/requests, and to establish a set process for communication. With that at minimum you will start getting consistent feedback. From there you can tweak it to get your specific needs.
As an aside, rather than just using e-mail for your communication, I strongly recommend going to smething like BaseCamp for a project management tool. I find that it helps greatly with keeping messages, documentation, and timelines communicated to the client.
If you are using Team Foundation Server, I recommend you to install TeamPlain Web Access. They allow you to expose a web interface to your TFS project. The only things left to do, is give rights to your client and a username and a password.
Otherwise, there is some paying tools like FogBugz. Of course, the principal is having to bug reporting tools directly linked to your Source Control so that the developers can easily fix bugs.
Although I know of no specific tools (at least no open source ones), I suggest that you setup a system which will cover your overall requirements gathering and implementation process. Requirements could be tracked in the system, which would also contain the design documents (which could be "checked out from" and "committed to" the system). This way, you would tackle the problem of having multiple revisions of design documents around. Addionally, the design documents and the requirements could be tracked easily. If this system were linked to your source code management system, you would additionally ease your development process/requirements tracking.
Another possibility is to use two products in concert, here's our current setup with a team of 12:
osTicket for incoming requests from clients
Allows for issues to be handled by support staff and bugs to be verified
Status can be checked with just an email address and ticket ID
Typically users don't submit detailed enough bug reports so is a good first step
redmine for development tickets
Ticket created by QA or a developer if issue is a real bug
Provides solid enough project and release management
Is a solid step up from trac and mantis (and provides migration tools)
My company is planning to start a forum for our software product which the clients can refer for general FAQ's, problems etc.
Right now we are planning to have:-
User manuals.
Best practices for different section's of the application
Frequently faced problems.
Forum where user can discuss issues with development team.
Any other ideas?
Edit:-
We have RSS and E-mail notification subscription to the forum.
Forum where user can discuss issues
with development team.
I don't know if this is a euphemism for "issue tracker" but if not, make sure you include a way for people to submit bug/feature/enhancement reports and track them to completion. Nothing is worse than not being able to submit a bug report or being able to submit a bug report but only into a black hole.
Communication is key.
If you add an issue tracker as suggested by Kevin, your list seems pretty ok to me.
I'd also suggest that you do not start out with too many different services that require interaction from your side (e.g. your developers) at first - I've seen (too) many good initiatives die simply because nobody in the company had enough time e.g. for regular answering of the forum questions.
In your case, I guess "best practices", "frequent problems" and the forum will all consume regular time from your dev team if you want to keep them alive and up-to-date, especially in the beginning. So I would not add more services at the beginning but make sure to get these right (and you can always add more services later on if you find that the users need them :-).
You.
Show that you care about your customers.
Many useful tips at Creating passionate users blog.
I am looking for a simple system to manage inbound emails from a support mailbox for a group with about 3 support people. I've looked at OTRS which seems to have the features that we need. Unfortunately, so far the UI still looks like a confusing mess.
Are there any good FOSS tools that would meet this need? I've heard murmurings that something called fooogzeeebugzo might have similar features, but it seems quite expensive for such simple needs.
Did you try IssueBurner? It was designed for this purpose. You can forward your mailbox (e.g. support#yourcompany.com) to a IssueBurner group and you can track the inbound mails until they are closed.
Here is a link to their video: http://issueburner.com/a/video
I have to agree, Fogbugz is probably the best out there. I have used both the hosted version and the purchased version which I hosted. It is top-notch.
BugTracker.NET is free, open source, and widely used. It has integration with incoming email. In other words, it will accept an incoming email and turn it into a support ticket.
My company recently started using Mojo Helpdesk: www.mojohelpdesk.com. It's a hosted service, not FOSS, but it's pretty cheap and the interface is slick.
TicketDesk- C# issue tracking system and support system
http://www.codeplex.com/TicketDesk
TicketDesk is efficient and designed to do only one thing, facilitate communications between help desk staff and end users. The overriding design goal is to be as simple and frictionless for both users and help desk staff as is possible.
TicketDesk is an asp.net web application written in C# targeting the .net 3.5 framework. It includes a simple database with support for SQL 2005 Express or SQL Server 2005. It can leverage SQL server for membership and role based security or integrate with windows authentication and Active Directory groups.
RT - Request Tracker handles inbound mail. I'm working to add inbound mail support to TicketDesk, but that might be a little while before that makes it into a release.
FogBugz is great as others have mentioned. I use it for my bug/feature tracking system, but I like to separate out my support ticketing system for my support staff to use. Another tool that has great email integration also is called HelpSpot, they have hosted and non-hosted versions for purchase, depending on your budget. It has a lot of great features, that make the prices worth it. Take the tour and see for yourself.
Scope out SmarterTrack, Help Desk Software from SmarterTools:
We use FogBugz...er, "fooogzeeebugzo"...and while it may be a bit expensive for your needs, it works very well.
bugzilla is more of an issue tracker than a request tracker, but it can be configured to handle email-based status tracking. That said, I think Steven has it- RT is the standard recommendation for this that I've seen.
The on-demand version of Fogbugz is a pretty cheap option for just a few people, and works really well. We did that for a while before moving it inhouse.
I've used fogbugz for over 12 months now and more and more I'm finding one of the most valuable features is the in built email support. I've got an on demand account and I'm finding more and more that I don't even check my email in the morning as all my business correspondence is put straight into fogbugz.
I realize that FOSS is your primary desire and I definitely agree with this. If I were to limit myself to FOSS, I would go with RT 3.8, http://blog.bestpractical.com/2008/07/today-were-rele.html#screenshots
However, if you are willing to entertain commercial solutions and are looking for a Helpdesk-"ish" application. I just deployed WebHelpDesk with great success at my current employment, where I am the primary sysadmin and Corporate IT person. They just released a new version, 9.1.1 and it is very well done. The email integration is superb and beyond what I have seen with most other FOSS and commercial issue/bug trackers, given that it is built to run a Helpdesk and not be a software or source code issue tracker. It runs on Windows and *nix, they have a great demo and you can obtain a 30 day trial installer. I have become a big fan of this software and think it has a reasonable price of $250/year/technician (support person).
If you want more info on how we deployed it, please email me and I'd be happy to discuss it at length. I have no more connection with them than I am a very happy customer.
Thanks for all the tips. For the moment, I am looking heavily at eTicket as it was trivial to setup and seems to be developing nicely at the moment. I may look at RT as well, though.
I'll second the suggestion for RT. See my post here for more thoughts and details on our setup.
From my personal experience I can recommend using Bridgetrak.
It works pretty smooth in our environment and includes rich helpdesk functionality for powerful tickets tracking.
I have a lot of experience using this tools - feel free to ask any questions!
As most of the answers are a little bit outdated, I would definitely recommend OsTicket (http://osticket.com/), a great open source project that offers lots of customization and a user friendly interface.
I have been using it for the last two years and I would rather choose OsTicket than OTRS or RT.