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.
-
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.
Quote:
somewhere to describe the issue
Your office?
Quote:
somewhere to describe the fix
Your bosses office?
Quote:
a basic priority for the issue
One. It's always one.
Quote:
a basic classification for the issue (e.g., documentation issue, bug, feature request)
"Annoying"
Quote:
ability to search the issue/fix database
You want to repair databases, you go for it. What a consenting database and developer do in their own cubicle is nobodies business but their own.
Quote:
record who fixed the issue, and when
Nah, MP3 is a much better idea.
Quote:
record who tested the fix, and when
See above. See above again.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
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 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
-
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
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!!
-
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.
Roll thine own.
-
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.
-
Roll thine own.
-
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!!
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
-
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!!
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
-
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
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?
-
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.
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
-
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?
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
-
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
-
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
our dev team is 12 people.
-
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.
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.
-
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 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.
-
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.
You can find some here: jira-alternatives[^] And also here: best-bug-issue-tracking-tools-for-small-development-teams[^]
-
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 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?
MessageBox.Show(!string.IsNullOrWhiteSpace(_signature)
? "This is my signature: " + Environment.NewLine + _signature
: "404-Signature not found"); -
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
