|
|
|
|
In the last year I've used Teamforge and Redmine. In the past I've also used irRational Clearquest  , SharePoint (worked great as a simple bug list, especially since SP was familiar to our non-technical users), and (many years ago) Visual Intercept. Currently IT is soliciting interest in how many teams would be interested in replacing TeamForge with JIRA. Although they're currently calling it "voluntary" I expect that within a year they'll decide it'd be cheaper to shut down teamforge than to pay licensing fees for two trackers and force everyone else to switch as well.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Our change request system (bugs, enhancements, new functionality) is built into the application (client/server, .NET, SQL Server). Users can request a change from within the application and it then goes through a management/development process. Works great for us.
|
|
|
|
|
We use mantis. It's not amazing, but it works.
We know PHP and have modified the workflow (shocked it is not data driven to configure).
But after customizing it and using it since it was Beta, it is kind of second nature.
Our applications allow the end user to email in issues with/logs if they have crashes or problems.
We had to put a simple script on the server to pull them into mantis.
I agree. They all have drawbacks. We use a process where we RESOLVE things, and then
the clients CLOSE them (okay, we close them during an interactive meeting with the Clients,
as they confirm the resolved issue is published).
We use it for 3 reasons:
1) Visibility/Planning
2) Communication/Process
3) EOM and EOY Summaries. Very cool to to show 70% of annual effort was on New Features!
|
|
|
|
|
Thanks for the info.
I had stumbled upon Mantis also and thought it looked relatively decent.
Then I noticed that it is implemented in PHP. 'nuff said. 
|
|
|
|
|
We use Mantis company-wide. IMO it is adequate.
Cheers,
Mike Fidler
"I intend to live forever - so far, so good." Steven Wright
"I almost had a psychic girlfriend but she left me before we met." Also Steven Wright
|
|
|
|
|
Thanks. Mantis was one I stumbled upon and was taking a look at. Then I saw it was PHP. 'nuff said.
|
|
|
|
|
We use TFS for story management, defect tracking, source control and continuous integration. A one-stop shop that meets all our needs. IMHO, it works well. Very well.
/ravi
|
|
|
|
|
Very good to hear someone say they have an effective system in place.
We'll just keep emailing our bugs around. 
Manager: "Why does this crash occur in production?"
Dev: "Oh, I guess I missed the email with that bug."
|
|
|
|
|
built my own a few years back to allow others to send me bug fixes, and feature requests. They can view the status on their own machines.
The program does what it's good at; I've felt tempted to extend it further but can't justify the time (yet )
|
|
|
|
|
I order of the most I like to the ones I hate:
1- Trac: you can host it, you can add you plugins, it has wiki, there are hosted sites that can give you one repository, but can look old compared to today social media, but dude you don't want facebook if you are working.
2- Jira: could be better, have some features that I hate and consider useless. can be hosted or bought as a service. You can handle a lot of projects with this, have integration with all they products to give more services (Confluense...)
3- TFS: very good if you have a good admin working over it. The integration with VS is wonderful.
4- Spiceworks: a lower version of Jira, we ate it cause gave us a lot of problems.
|
|
|
|
|
Great info. Thanks for the feed back. I think a lot of the difficulties with all of these systems is just the learning curve/ setup curve for getting everything set the way you want to use them.
|
|
|
|
|
|
Thanks for chiming in on this.
|
|
|
|
|
|
Wonderfull images again, the universe is such a beauty
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Why are you complaining my question if you can't answer. Due to you i am not getting solution of my problem.
|
|
|
|
|
I have explained numerous times. Have you seen my comments?
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
The only one I see complaining is you.
You have not demonstrated that you are capable of following directions (See top of this page). The suggestions for posting this question in the correct forum are appropriate. You are not getting “solutions” because you have not posted your query in the Q&A forums where you will generate responses to help you with your question.
I suugest you rethink your approach here, and please read very carefully the Lounge Rules at the top of this page.
Regards.
It was broke, so I fixed it.
|
|
|
|
|
(Actually there was a QA question, but so poorly phrased that it was closed - but not without proper comment!!!)
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
i have posted in question/asnwer section. but you have closed by complaining.
|
|
|
|
|
and whining here is gonna make things better?
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Following around your posts/questions, I can see that you posted your question in such a way that people didn't think it could be answered as it was poorly formed. You might want to try rephrasing your question and I'm sure that people might answer it. BTW - the big hint here, think about what InProc state management means when you're running across multiple servers/VMs and think about if there's a more appropriate state management option available in a load balanced environment.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
