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.

    N Offline
    N Offline
    Nemanja Trifunovic
    wrote on last edited by
    #6

    The best I've used so far is Trac[^] but everybody uses JIRA nowadays...

    utf8-cpp

    1 Reply Last reply
    0
    • P PIEBALDconsult

      Roll thine own.

      K Offline
      K Offline
      Kyudos
      wrote on last edited by
      #7

      This option is definitely on the table :-D

      1 Reply Last reply
      0
      • S Slacker007

        We do everything with DevOps. user stories and bugs features, test cases, etc. source control with Git Code reviews auto build pipelines and deployments ... everything. Love it!!

        R Offline
        R Offline
        Ravi Bhavnani
        wrote on last edited by
        #8

        We also do the same.  For my personal projects, I prefer to use TFS. /ravi

        My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

        1 Reply Last reply
        0
        • S Slacker007

          We do everything with DevOps. user stories and bugs features, test cases, etc. source control with Git Code reviews auto build pipelines and deployments ... everything. Love it!!

          M Offline
          M Offline
          Mycroft Holmes
          wrote on last edited by
          #9

          And how does the size of your team compare to 2.5 devs? :laugh:

          Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP

          S 1 Reply Last reply
          0
          • R Ravi Bhavnani

            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

            K Offline
            K Offline
            Kyudos
            wrote on last edited by
            #10

            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?

            R J 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.

              L Offline
              L Offline
              Lost User
              wrote on last edited by
              #11

              MS Project. Includes scheduling. Costing.

              "Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I

              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?

                R Offline
                R Offline
                Ravi Bhavnani
                wrote on last edited by
                #12

                At work, we host ADO onsite, but are moving towards hosting on the MS cloud.  For my personal projects, I've always used the MS cloud. /ravi

                My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                L 1 Reply Last reply
                0
                • R Ravi Bhavnani

                  At work, we host ADO onsite, but are moving towards hosting on the MS cloud.  For my personal projects, I've always used the MS cloud. /ravi

                  My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com

                  L Offline
                  L Offline
                  Lost User
                  wrote on last edited by
                  #13

                  Just want to add that it's been renamed to 'Azure DevOps'. :)

                  R 1 Reply Last reply
                  0
                  • M Mycroft Holmes

                    And how does the size of your team compare to 2.5 devs? :laugh:

                    Never underestimate the power of human stupidity - RAH I'm old. I know stuff - JSOP

                    S Offline
                    S Offline
                    Slacker007
                    wrote on last edited by
                    #14

                    our dev team is 12 people.

                    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.

                      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
                                          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