Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. The Lounge
  3. Issue Tracking Tools

Issue Tracking Tools

Scheduled Pinned Locked Moved The Lounge
helpcollaborationdatabasetestingbeta-testing
42 Posts 33 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Kyudos

    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.

    E Offline
    E Offline
    englebart
    wrote on last edited by
    #15

    You could create a “tracking” folder in your SVN where you check in a text or markdown file along with the changes. Have a standard template that you clone. Consider simple http header like format for searching via regex. It will be committed on the same revision with the changes. If you have your work files on an SSD this would be viable for 10,000+ commits or so (for searching) Create project/epic/yearly sub folders to help organize if desired.

    1 Reply Last reply
    0
    • K Kyudos

      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.

      Y Offline
      Y Offline
      yacCarsten
      wrote on last edited by
      #16

      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.

      M 1 Reply Last reply
      0
      • K Kyudos

        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.

        J Offline
        J Offline
        Jacquers
        wrote on last edited by
        #17

        Put a TODO comment in the code :P But be sure to add a description :laugh:

        J 1 Reply Last reply
        0
        • K Kyudos

          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.

          R Offline
          R Offline
          RickZeeland
          wrote on last edited by
          #18

          You can find some here: jira-alternatives[^] And also here: best-bug-issue-tracking-tools-for-small-development-teams[^]

          1 Reply Last reply
          0
          • K Kyudos

            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.

            H Offline
            H Offline
            HobbyProggy
            wrote on last edited by
            #19

            I am a fan of the JetBrains Tools and therefore we (3 dev's) use JetBrains YouTrack. It's on premise, free for 10 Dev's and you can but do not have to use the complete functionality with timereporting and so on. Additionally if you may later want that you could directly connect their tool for code reviews, the build server application for CI and the so called HUB as the main manager for logins and projects. But as far as i know you'd get most of this also by gitLab, which i think should also be free up to a certain amount?

            Rules for the FOSW ![^]

            MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
            ? "This is my signature: " + Environment.NewLine + _signature
            : "404-Signature not found");

            1 Reply Last reply
            0
            • J Jacquers

              Put a TODO comment in the code :P But be sure to add a description :laugh:

              J Offline
              J Offline
              Johnny J
              wrote on last edited by
              #20

              It's much more fun and sportsmanlike to omit the description... :-D

              Anything that is unrelated to elephants is irrelephant
              Anonymous
              -----
              The problem with quotes on the internet is that you can never tell if they're genuine
              Winston Churchill, 1944
              -----
              Never argue with a fool. Onlookers may not be able to tell the difference.
              Mark Twain

              1 Reply Last reply
              0
              • K Kyudos

                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.

                M Offline
                M Offline
                Mehdi Gholam
                wrote on last edited by
                #21

                Try Gitea gitea | Gitea[^] a self hosted github clone.

                Exception up = new Exception("Something is really wrong."); throw up;

                R S 2 Replies Last reply
                0
                • K Kyudos

                  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.

                  D Offline
                  D Offline
                  den2k88
                  wrote on last edited by
                  #22

                  Redmine has a free version, usable for comemrcial purpose. It's not wonderful but it works.

                  GCS d--(d-) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++*      Weapons extension: ma- k++ F+2 X

                  1 Reply Last reply
                  0
                  • M Mehdi Gholam

                    Try Gitea gitea | Gitea[^] a self hosted github clone.

                    Exception up = new Exception("Something is really wrong."); throw up;

                    R Offline
                    R Offline
                    RickZeeland
                    wrote on last edited by
                    #23

                    We are using Gitea on a Windows server with a PostgreSQL database for years now and it's very stable. If you don't want to self-host it, there is a free hosted version: Codeberg[^]

                    1 Reply Last reply
                    0
                    • K Kyudos

                      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.

                      D Offline
                      D Offline
                      Davyd McColl
                      wrote on last edited by
                      #24

                      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

                      1 Reply Last reply
                      0
                      • K Kyudos

                        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.

                        C Offline
                        C Offline
                        CHill60
                        wrote on last edited by
                        #25

                        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

                        J 1 Reply Last reply
                        0
                        • K Kyudos

                          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.

                          J Offline
                          J Offline
                          Jari Pakarinen 2021
                          wrote on last edited by
                          #26

                          YouTrack: Project management for all your teams[^] Free for teams less than 10 persons. Cloud or on-prem install.

                          1 Reply Last reply
                          0
                          • K Kyudos

                            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.

                            M Offline
                            M Offline
                            Member 13932523
                            wrote on last edited by
                            #27

                            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.

                            1 Reply Last reply
                            0
                            • C CHill60

                              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

                              J Offline
                              J Offline
                              Jorgen Andersson
                              wrote on last edited by
                              #28

                              So what do you do nowadays?

                              Wrong is evil and must be defeated. - Jeff Ello

                              C 1 Reply Last reply
                              0
                              • K Kyudos

                                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.

                                C Offline
                                C Offline
                                Cpichols
                                wrote on last edited by
                                #29

                                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.

                                1 Reply Last reply
                                0
                                • K Kyudos

                                  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.

                                  S Offline
                                  S Offline
                                  Slow Eddie
                                  wrote on last edited by
                                  #30

                                  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

                                  1 Reply Last reply
                                  0
                                  • K Kyudos

                                    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?

                                    J Offline
                                    J Offline
                                    John Bevan
                                    wrote on last edited by
                                    #31

                                    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.

                                    1 Reply Last reply
                                    0
                                    • K Kyudos

                                      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.

                                      J Offline
                                      J Offline
                                      James Taylor C
                                      wrote on last edited by
                                      #32

                                      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[^]

                                      1 Reply Last reply
                                      0
                                      • J Jorgen Andersson

                                        So what do you do nowadays?

                                        Wrong is evil and must be defeated. - Jeff Ello

                                        C Offline
                                        C Offline
                                        CHill60
                                        wrote on last edited by
                                        #33

                                        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:

                                        1 Reply Last reply
                                        0
                                        • M Mehdi Gholam

                                          Try Gitea gitea | Gitea[^] a self hosted github clone.

                                          Exception up = new Exception("Something is really wrong."); throw up;

                                          S Offline
                                          S Offline
                                          Stuart Dootson
                                          wrote on last edited by
                                          #34

                                          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

                                          1 Reply Last reply
                                          0
                                          Reply
                                          • Reply as topic
                                          Log in to reply
                                          • Oldest to Newest
                                          • Newest to Oldest
                                          • Most Votes


                                          • Login

                                          • Don't have an account? Register

                                          • Login or register to search.
                                          • First post
                                            Last post
                                          0
                                          • Categories
                                          • Recent
                                          • Tags
                                          • Popular
                                          • World
                                          • Users
                                          • Groups