Bug types:
- hardware 1%
- software 5%
- peopleware 94%

My favorite word to read in client-written requirement documentation: "Etc"

...Do I look like I have a crystal f-ing ball?

fuck..fuck..FUCK..FUCK YOU MANTIS!!!
fuck you and your fucking invalid security token... fucking cunt...
yeah i love extracting my notes from POST data via the browser dev console cause you fucking delete it when hitting the back button...
THANKS FOR NOTHING

xxx: Thank you for your pull request, it's nice!
yyy: You are welcome.

*xxx: Rewriting it from scratch.

I definitely need a button to order pizza while driving home.

Sweet taste of Java

After my second 12 hour day this week working on 4 little Mantis tickets that circled around for like 5 times...

Fuck computers.
Fuck technology.
SUCK MY DICK.

Have a nice evening everyone.

git rebase -i HEAD~48

* children are crying on the background

I'm so fed up with our current "Bugtracking"system.

In the past we've been using mantis bt.
A heavily modified version though. Exactly specified to the developers needs with an integration to our own desktop software, which has time tracking and reports.

Also we had a separate mantis for everyone else.
Support guys and so on.

Everything was working fine.

But then "someone" decided that we shouldn't have two different mantis versions running and should integrate the support into the developer version.

Well ok. Makes sense.
So we changed mantis a bit so we can better differentiate the projects and tasks.

But "someone" is just too fucking dumb to understand how mantis works.

So after some time "someone" decided we won't be using mantis anymore, but a steaming pile of shit we have no control of how it works.
(It's called Wrike if you want to take a look at that)

It's completely useless if you want to use it as a bugtracker.
Maybe it works for the support guys I thought and asked them.
Seems they barely use it. They rather write everything down on paper and manually write their times into our desktop software now. Fucking awesome!

And even better. "Someone" isn't using this confusing and totally useless shit either.

I'm fed up.
I'm gonna set up a new version of mantis write everything the wrike api gives me into it.
Also need to modify it, so it works with our desktop software again.
And an integration with our Gitlab would be nice too I guess.
(Can't use the old mantis version we had, because it didn't have projects inside projects, which because of Wrike now is needed to sync)

Uh...
Lots of work...
So much time wasted...
And so much time still has to be wasted...

What should I do with a guy, who rejected help, promised to do the work and just didn't even try to do it?

hhh: Where do you see yourself in five years?
ddd: Moving Fuji mountain of course.

Not so huge amount of monitors XD

So I´m still working on that Sync to get rid of this abomination called Wrike.

Now I have a problem.

To be able to sync mantis with our software I need to be able to create projects in mantis through the API.
No problem.
But then again, I need to link custom fields to that just created project.
The mantis API apparently doesn´t have that.

I now have two options:
1. I expose the custom field functions myself on the REST api.

2. I gain direct access to the mysql database and do it within my sync job in the database.

Well I´m not a web developer. Like, at all.
But I thought: Hey how hard can it be?
So I got an Apache server with php, mysql and XDebug running with VSCode.
Works better than expected.

But now that I have actually seen the mantis code, I´m seriously considering number 2 again...

Fucking php...

We have an automated check for code coverage. One of the rules "It shouldn't decrease after the change".

And then you delete unused code from the class :)

Now total number of lines decreases and % of uncovered lines increases :/

ttt: I've found a bug, should I report it?
ddd: No.
ttt: But why?! It's a bug!
ddd: Why did you even ask?

Client request of the day:

Client asks to omit data based on lack of X.

...

Client asks to preload all data with X.

We're slowly migrating to VSTS (sigh) from Mantis and SVN for tasks management and code repo.
It's been 4 months now and we still have to move the code from SVN to GIT, asked management when they plan to do that and they still give no ETA, and when asked to make sure our commits stays intact after the transfer I got told "no need for that we're just gonna copypaste the last version of the source code". And most likely the local SVN server we're using is gonna be dismissed.

On top of that, by the way they want to use it, VSTS is being terrible for tracking stuff. I'm so used with other tools at home for some side projects and even though I expressed my concern about VSTS I got ignored over and over...

Bonus (not so) fun fact: branches are something mythic here so everyone else commits straight to master and it's a pain in the ass everytime, because people happen to break things most of the time.

And no, unfortunately this is not a small company.

Send halp please 😭