Issue Tracking Tools
-
So what do you do nowadays?
Wrong is evil and must be defeated. - Jeff Ello
I retired for a couple of years, then applied to a local firm as a VBA "Developer" (quotes mine). The intention was to take it easy but still have an income to pay for my love of travel. Once they found out I used to work in IT and was quite handy with SQL, I ended up with more and more "technical" stuff. Now I'm in a small, multi-skilled business-side team that advises on Process Improvement, RPA Automation, Insights & MI as well best use of Office tools, Power suite and general geekiness :-D I did manage to get SSMS installed - probably because it's free - but long gone are the days of being able to knock something up in C#. Can't even use any of the scripting languages as I'm not on the white list :sigh:
-
Try Gitea gitea | Gitea[^] a self hosted github clone.
Exception up = new Exception("Something is really wrong."); throw up;
I'll add another 👍 for Gitea - dead easy to install and administer (I connected it to our AD domain in about 2 minutes) and pretty simple to use too.
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
We use IT Help Desk Software and Ticketing System | Track-It![^] for a team of 4. Easy to use and its database sits in our SQL Server.
// TODO: Insert something here
Top ten reasons why I'm lazy 1.
-
I use TFS (ADO Dev Ops) hosted at Microsoft. My cost is zero, as is the cost for companies of less than 5 persons. Feel free to ping me and I can give you a demo. Setup took zero units of time. /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
It is free for 5 people, but those using licensed VS also get free access I believe. So those using VS with Azure DevOps don't count to the 5 person limit for free access. At least that is my understanding...
-
-
We are looking for a simple issue tracking system to improve the formality/structure of our bug reporting / fixing / testing cycle. We don't really need anything complicated like SLA management, time spent on issue, milestones etc. Things we would like: - somewhere to describe the issue - somewhere to describe the fix - a basic priority for the issue - a basic classification for the issue (e.g., documentation issue, bug, feature request) - ability to search the issue/fix database - record who fixed the issue, and when - record who tested the fix, and when - SVN integration would be nice (but somewhere to record the commits related to the fix would do) Most of the things we've looked at so far are way more complicated (and/or expensive) than we require (we have 2.5 devs and 1 support person, developing a very complex, niche technical product with a 20+yr old code-base), but I'm interested to know what others are using (especially if you are in a small team). Cheers.
I use a product I developed for a client some years ago. Admittedly, it needs some updating, but it covers the basic things you want to do. You can look at the product and download a demo at Lucid Help Desk[^] There is a client-server version available, which is not listed in the purchase page.
-
We are looking for a simple issue tracking system to improve the formality/structure of our bug reporting / fixing / testing cycle. We don't really need anything complicated like SLA management, time spent on issue, milestones etc. Things we would like: - somewhere to describe the issue - somewhere to describe the fix - a basic priority for the issue - a basic classification for the issue (e.g., documentation issue, bug, feature request) - ability to search the issue/fix database - record who fixed the issue, and when - record who tested the fix, and when - SVN integration would be nice (but somewhere to record the commits related to the fix would do) Most of the things we've looked at so far are way more complicated (and/or expensive) than we require (we have 2.5 devs and 1 support person, developing a very complex, niche technical product with a 20+yr old code-base), but I'm interested to know what others are using (especially if you are in a small team). Cheers.
We wrote our own app to do that. You get just what you want that way. But, I think that there are open source help desk apps available.
-
We are looking for a simple issue tracking system to improve the formality/structure of our bug reporting / fixing / testing cycle. We don't really need anything complicated like SLA management, time spent on issue, milestones etc. Things we would like: - somewhere to describe the issue - somewhere to describe the fix - a basic priority for the issue - a basic classification for the issue (e.g., documentation issue, bug, feature request) - ability to search the issue/fix database - record who fixed the issue, and when - record who tested the fix, and when - SVN integration would be nice (but somewhere to record the commits related to the fix would do) Most of the things we've looked at so far are way more complicated (and/or expensive) than we require (we have 2.5 devs and 1 support person, developing a very complex, niche technical product with a 20+yr old code-base), but I'm interested to know what others are using (especially if you are in a small team). Cheers.
Our IT uses Roundup[^] to track it's own internal issues. Small footprint, easy to use, easy to maintain. We don't use any integration, but it is possible[^]
-
We are looking for a simple issue tracking system to improve the formality/structure of our bug reporting / fixing / testing cycle. We don't really need anything complicated like SLA management, time spent on issue, milestones etc. Things we would like: - somewhere to describe the issue - somewhere to describe the fix - a basic priority for the issue - a basic classification for the issue (e.g., documentation issue, bug, feature request) - ability to search the issue/fix database - record who fixed the issue, and when - record who tested the fix, and when - SVN integration would be nice (but somewhere to record the commits related to the fix would do) Most of the things we've looked at so far are way more complicated (and/or expensive) than we require (we have 2.5 devs and 1 support person, developing a very complex, niche technical product with a 20+yr old code-base), but I'm interested to know what others are using (especially if you are in a small team). Cheers.
How about a big honkin' Excel spreadsheet sitting in a shared network folder on Fred's laptop? [whistles and wanders quietly away]
Software Zen:
delete this; -
We are looking for a simple issue tracking system to improve the formality/structure of our bug reporting / fixing / testing cycle. We don't really need anything complicated like SLA management, time spent on issue, milestones etc. Things we would like: - somewhere to describe the issue - somewhere to describe the fix - a basic priority for the issue - a basic classification for the issue (e.g., documentation issue, bug, feature request) - ability to search the issue/fix database - record who fixed the issue, and when - record who tested the fix, and when - SVN integration would be nice (but somewhere to record the commits related to the fix would do) Most of the things we've looked at so far are way more complicated (and/or expensive) than we require (we have 2.5 devs and 1 support person, developing a very complex, niche technical product with a 20+yr old code-base), but I'm interested to know what others are using (especially if you are in a small team). Cheers.
Hello, I can recommend redmine. https://www.redmine.org I have used it for years as a free install on a local linux box. Stores its data within PostgreSQL, MySQL or MariaDB. Links/integrates to various source control programs. I have it linked to svn and git. So you can see the check ins against the tickets. And review the changes without ever leaving redmine. There are hosts for it too, though i've never used them so can't suggest one. Hope that helps. Cheerio