|
|
That's the polite anagram 
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
But what does "no oat" mean? 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Now now Richard 
"Life should not be a journey to the grave with the intention of arriving safely in a pretty and well-preserved body, but rather to skid in broadside in a cloud of smoke, thoroughly used up, totally worn out, and loudly proclaiming “Wow! What a Ride!" - Hunter S Thompson - RIP
|
|
|
|
|
"You're out of porridge, dear".
"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!
|
|
|
|
|
Isn't it time for someone to guess SCROTUM?
>64
Some days the dragon wins. Suck it up.
|
|
|
|
|
That someone is not active here anymore.
"It is easy to decipher extraterrestrial signals after deciphering Javascript and VB6 themselves.", ISanti[ ^]
|
|
|
|
|
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!
|
|
|
|
|
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
|
|
|
|
|
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
|
|
|
|
|
And how does the size of your team compare to 2.5 devs?
Never underestimate the power of human stupidity -
RAH
I'm old. I know stuff - JSOP
|
|
|
|
|
our dev team is 12 people.
|
|
|
|
|
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
|
|
|
|
|
Just want to add that it's been renamed to 'Azure DevOps'. 
|
|
|
|
|
Yes, that's what I meant by ADO (not to be confused with this[^]).
/ravi
|
|
|
|
|
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.
|
|
|
|
|
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...
|
|
|
|
|
|
This option is definitely on the table
|
|
|
|
|
The best I've used so far is Trac[^] but everybody uses JIRA nowadays...
|
|
|
|
|
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
|
|
|
|
|
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.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
