My team needs a bugtracker
-
Need a bug tracker.
Needs to run on Windows.
Preferably MSSQL DB but I may be willing to entertain opensauce databases.
DB Schema should not be shit so I can do adhoc reporting and dashboarding (or it needs a top notch API).
Needs to be capable of being migrated between servers without a PhD (FUCKING JIRA)
Must be on premises hosted.
Integration with TFS would be nice.
Must be able to authenticate against Active Directory.We're a small team. Our methodology is basically adhoc with many parallel projects in all phases of the lifecycle at all times.
I am less concerned with nonbug issue tracking - that shit goes on a kanban on the physical wall.
We've tried JIRA but it's too heavyweight.
-
If you already have TFS, why not use that?
-
Oh. I forgot to mention. Our TFS is administered by another team. The only features they allow use of right now is the source control. Because the rest is still new to them. A trial for the rest of the product will be run after the update to tfs2013.
-
The rest of those features (and the integration therein) are what make it a compelling choice.
We (team of ~10) use TFS for bug tracking, product backlog and source control. It's very nice to be able to link changesets to bugs and/or backlog items. You can create different entry templates for bugs and backlog items. You can set up custom "queries" which can be public or private to see who's working on what, and get basic reports without even touching the DB. And since it runs on MSSQL... that should open the door to ad-hoc reporting.
-
Therefore I would bug them for access to the workitem side of TFS. Wait, they let you check in without a work item?
-
Migration from very old TFS from before work items, so the defaults are very old.
Maybe I should put up a TFS in my sandbox and play with it so I know specifically what I'm missing out on and can make an informed case for opening up the Corp system. (I've never used TFS in all of its glory).
-
Good luck!
I personally tried to make a strong case to fully migrate to TFS (from JIRA and MKS).- Provided a full binder of info (That I created, not including their "PMO" provided junk), totaling approximately 200 pages, including migration of existing tickets, adaptation of current deployment procedures, communications, translations (of workflows), the works
- Asked for access to a demo instance (Got team-admin privs, not that great for what I needed to do)
- Held meetings, created demonstration powerpoints, and participated in their "training" sessions.
- Got the support of my peers and supervisor to help guide the process.
End results? We dun f'ed up everything.
- Still using JIRA. Work documentation now has the tendency to appear (incompletely) in at least three places.
- Haven't heard from the PMO group for a year (what do they even do?!)
- EVERYONE is lost and doing Bad Things in TFS, because my guidance and best practices were never approved, but there wasn't clear guidance provided in lieu thereof.
- Seriously, BAD THINGS. Whoever keeps checking in individual files (despite being part of the same set of changes) is an Arse with a capital hole!
If you can do it, go for it! But be careful your efforts aren't wasted....
-
-
Project Management Office.
They're supposed to develop and maintain procedures and stuff for how we do our projects.
-
Integration with TFS would be nice.
???
Why not use TFS's bug tracker?
Oh. I forgot to mention. Our TFS is administered by another team. The only features they allow use of right now is the source control. Because the rest is still new to them. A trial for the rest of the product will be run after the update to tfs2013.
... oh.
Wait, they're not on 2013 now? Do you work for a bank or government? What the fuck are they waiting for?
-
What the fuck are they waiting for?
"Stability" maybe? Who knows. I ask myself that every time it takes six months to review a test report that was Urgent Must Be Done Yesterday so I can get it approved for promotion to production...
-
The team that owns TFS is our Web hosting group. They Uh. Don't have a horse in the development race. We were on 2008 until they were held at gunpoint.
-
The team that owns TFS is our Web hosting group. They Uh. Don't have a horse in the development race. We were on 2008 until they were held at gunpoint.
I prefer to think you meant that literally. "Oh no, Jim's got hostages, and he's going to start shooting one PM or BA an hour until someone upgrades TFS!"
"Let's hold off a while..."
-
More or less.
Most IT teams in this company could absorb 90 percent casualties without meaningful damage.
-
ASP .NET and MS-SQL, fairly simple, easy to use and easy to install (last time I used it which was admittedly a few years ago).
(Personally I prefer Redmine these days but the joys of setting up a Ruby on Rails site are enough to make me want to leave the computing world behind completely)
-
Discourse, obviously.
-
... oh.
Wait, they're not on 2013 now? Do you work for a bank or government? What the fuck are they waiting for?
Maybe he has a lazy sysadmin team?
I find it amusing that my office only moved to TFS2013 two weeks ago and are now planning on moving to TFS 2015 in 3 months.
...except that I'm one of a small team of Java developers in a mostly .NET office. We're still using SVN for our code even though we use TFS as a bug/task tracker. Although I just had a meeting with our sysadmins about importing from SVN into TFS...
-
Oooooh maybe you should write a twitter competitor in a language and platform you don't know and understand and use that?
-
Maybe he has a lazy sysadmin team?
If you've forgotten, he covered it here:
-
Did we go to 2013 already? I've already forgotten the fine points of that flustercuck.
-
A trial for the rest of the product will be run after the update to tfs2013.
I was about to
this, but I see Blakey got there first.We're unhappy here that we aren't on 2015, because of the updates to the task boards.
-
We're unhappy here that we aren't on 2015, because of the updates to the task boards.
We're still sitting on VS2008. Because CEF1. And XP support.
-
We're still sitting on VS2008
We're only now phasing out applications the company i work for wrote with VS2003.
-
VS2003
Forget VS2003, we're phasing out Access '97!
-
I mean, if redmine doesn't suck in a Microsoft world, I can certainly argue with Ruby for a few days.
-
phasing out Access '97
I wish.
Filed under: seriously though, some of my work does require me to dive into a MDB front-end originally built in Access 2003
-
So I just poked around in TFS. It may not be officially sanctioned, but my team has issues back from when one guy apparently made his own work items just for himself 10 years ago. I just took over and closed his long obsolete work items and will henceforth use this to pretend that we have ALWAYS used TFS work items when someone comes screaming at me for it.
-
I just took over and closed his long obsolete work items
Lol, he probably got notifications for that!
I'm the only one on my team actually using workitems correctly (everyone else just makes orphan tasks so they can check-in, if they want to).Our burndown charts never looked better! (Yes I know this isn't a burndown chart, no I'm not allowed access to the darn report server to actually get it)
-
Nah he's long since gone from the company.
The setup is super primitive with only active and closed statuses but I can deal with that. It's pretty much how we work anyway.
-
And XP support.
I had a customer ask me this summer if our product worked on newer versions than XP, because a lot of our screenshots are old.
I said "well, I'm using Windows 10 at the moment and it runs fine...".
-
Why does your documentation/marketing have screenshots from the XP era?
-
Why does your documentation/marketing have screenshots from the XP era?
Because it's a small company with under a dozen people, and while I wish it wasn't the case, nobody's got time to go back just to re-take all the screenshots. Although I'm tempted.
-
You don't find that extremely embarassing? 1) that you haven't updated your materials in so long, and 2) that your UI hasn't changed enough to require it?
-
You don't find that extremely embarassing? 1) that you haven't updated your materials in so long, and 2) that your UI hasn't changed enough to require it?
Yes, I do, but like I said, who's got time? I refreshed a few of the pictures when I had a chance--in fact, I told someone who was going to do it to let me instead, because I could take Win10 screenshots instead of Win7 ones. Then I never got to do it.
I work for a small company that got bought out by a competitor; they're want to kill the product, except for the unfortunate circumstance that ours is generally better, and the clients mostly flat-out refuse to switch. So the corporate office denies us resources (for example, not hiring replacements for people who quit/retire) in the hopes of strangling the product.
But it's a 9-5 job that requires essentially no overtime, it's a hair over a mile from home, it's not full of the kind of bullshit wtfs @Weng or @Snoofle put up with, and it pays decently. When it becomes annoying enough, I'll leave. It hasn't quite reached that point.
-
Well I'm embarrassed FOR you.
-
Spend a session with Steps Recorder?
psr.exe, they didn't nuke that yet!
-
Well I'm embarrassed FOR you.
That makes two of us.
Like I said, I'd love to update the docs, and if I can squeeze in time to do it here and there I will. But the product may be dead in a year or two anyway.
-
Steps Recorder?
I have never even heard of that before just now, but it wouldn't really fit in. We're still
using CHMs for help.I spent years trying to get management to let me modernize the app, and they didn't care. Then I just started making improvements wherever I can get away with it.
-
I have never even heard of that before just now,
Yeah it's a nifty tool MS recommends you to use to send people "what went wrong" when having issues. I think it was introduced in Vista.You can extract the jpg files from the files it produces I think, if it makes any difference. IIRC they're just mhtml files zipped (mime-encoded html, so like an email).
-
But is it up to the level of bullshit WTFs I put up with?
-
But is it up to the level of bullshit WTFs I put up with?
Not hardly. It's just a bunch of mainly older people afraid of scary modern concepts like source control, who are also fairly hidebound and don't know it. I even have my own office--I worked in a place once that put the devs in 3-foot cubicles right next to telemarketers.
-
It just occurred to me that not one of you cheeky bastards suggested Discourse.
-
-
my office only moved to TFS2013 two weeks ago and are now planning on moving to TF2
How do you use Team Fortress 2 as a bug tracker?It just occurred to me that not one of you cheeky bastards suggested Discourse.
Except for
@CHUDbert said:Discourse, obviously.
I was going to, but saw @CHUDbert had beaten me to it.
-
It just occurred to me that not one of you cheeky bastards suggested Discourse.
Have you considered using Quake III? I think it'll make a much better bugtracker than Discourse...
Filed under: bug was exploded by a vore.
-
How "light" do you want it to be?
If all you need is a better Post-it board you might want to look at Trello. Since you can make multiple stacks of cards you can organize it any way you want to.
EDIT:
I forgot it needs to be hosted on premises... Still, maybe there are clones which can be installed...
-
-
How do you use Team Fortress 2
Obviously they're using Team Four Star's 2013 video catalog
-
.... Am I supposed to be able to unilaterally declare myself a project administrator? Because I just did. How fucking grossly misconfigured is this?
-
I don't recall but I think if you are in the TFS Administrators group you can grant all lesser privileges.
https://msdn.microsoft.com/en-us/library/ms252587.aspxThe network
s probably couldn't be bothered to learn how to admin TFS and granted god-mode to all developers.
