Issue Tracking Tools
-
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.
Trello. Don't skip just yet (: - describe the issue and fixes on a card - have entire conversations there if you like - cards can have custom fields - so you end up with a drop-down on the card for stuff like priority, classification - search your board any time for text on cards or people associated with those cards (probably on custom fields too - I have never tried) - the ability to place cards in lanes such as "incoming", "triaged", "work in progress", "fixed", "deployed" and associate board members with cards - SVN integration is one I'm not sure about - we link pull requests, branches, etc from Github there, so I guess if your SVN server exposes a web interface, you could deep-link to commits and files Trello is really simple to use and can be expanded upon with power-ups as you need them. The company I work at, for instance, wrote email integration so you can use Trello like a help-desk or customer queries queue: you mail the associated address, the power-up creates cards, and comments on cards are mailed back to the people involved (it's called SendBoard and has a free tier, if you want to give it a go)
------------------------------------------------ If you say that getting the money is the most important thing You will spend your life completely wasting your time You will be doing things you don't like doing In order to go on living That is, to go on doing things you don't like doing Which is stupid. - Alan Watts https://www.youtube.com/watch?v=-gXTZM\_uPMY
-
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 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.
YouTrack: Project management for all your teams[^] Free for teams less than 10 persons. Cloud or on-prem install.
-
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.
Redmine is a solution to all the features you ask for. It is open source can be run out of a Docker container, onsite, for a 'free' option.
-
Since leaving IT and now have zero budget for real stuff, I just use Excel. It works, but probably only because we are a "team" of 2
So what do you do nowadays?
Wrong is evil and must be defeated. - Jeff Ello
-
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.
Git commits? We use asana for tasks, and we add subtasks and comments along the way. New issues get added to the product backlog section and tags get added for priority. As a task is picked up, the person doing the work assigns the task to him/herself, and others may be added as collaborators or assigned to subtasks within the main task. It's simple and searchable.
-
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 Excel, It works for me. simple to use, reliable..... Just create the columns you want, mine starts with the date. the rest is easy.
ed
-
Thanks I'm having a play with this - I like that I can hide the sections for projects, like the Repos since we wouldn't use them. It looks like this could be pared back to what we would want... will have to get the boss to look at it too. Still maybe not so keen on the info not being 'in house' so to speak - the advantages of working 'in the cloud' aren't that strong for me. EDIT - Ah! I see there is there 'Server' and the 'Services' so we can keep it in house. Are they otherwise the same?
There are some additional differences; e.g. server includes the ability to use categories (ways of grouping projects) whilst services just has the default category. That said; unless you have a good reason, going cloud is far better (normally I'm not a preacher for SaaS as I like the ability to be able to get into the DB to do reporting/investigations/data fixes where the UI doesn't allow easy access)... You only have a small team, so running up a dedicated server for this product, managing backups, keeping on top of patching, etc will all waste a lot of time and money given you can get all of that for free. You can also integrate it with your AAD or IdP if you want extra security (e.g. to help avoid leavers retaining access to the system) though even without that, it'll probably still be more secure than your on-prem servers unless you're really on top of security. Also - are you using source control today / if so what do you use for that; as there may be offerings that integrate better with your source control system which could better inform answers to your question. If not - that's the more important issue than the software you use to manage work items. Again, generally I don't believe in universal rules; but there's no good justification for not using some form of source control.
-
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 have used Mantis Bug Tracker[^] in the past. Very easy to host yourself on your own site, Windows server or Ubuntu server versions available.. Check out Mantis Virtual Machines[^]
-
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