Yesterday I decided to do some work with our issue tracker — I won’t name what issue tracking software we use, I don’t want to hurt anybody’s feelings. Our issues are divided into projects, projects are further sub-divided into components.
What I tried yesterday is just one thing: create a few issues. You’d say that’s a pretty difficult thing to get wrong. Also, it’s kind of an important feature to get right, you know, for an issue tracker.
Currently, I’m working on a component named “Message Import/Export”. I’m looking at the list of Message Import/Export related issues. Now I want to add a new issue to this component. So, let me see, how do I do that?
Ah right, there it is!
Now, guess… When I press the “Create Issue” link/button, what will it do?
If you guessed that it would open a panel to create a new issue, you’d be correct. Congratulations! However, will this panel have any sort of context awareness? We were looking at the list of issues of a particular component, after all:
Yeah, so that’s a no. I have to select the component by hand, again.
Alright, so let’s try something different. Let’s create a “sub-task” of an existing issue that is already part of the component. At least it should be able to guess I’d like the sub-task to be part of that same component, right?
Yeah, that’s another no.
Or is it?
When I create the sub-task, and I go to view it, it turns out that it did add it to the component of its parent.
So this issue creation panel has no intention of giving me any hint of what it’ll do when I hit that “Create” button.
Perhaps, when I go back to my first test, creating a completely new issue while looking at component issue will in fact secretly set the component right behind my back? That would be at least be somewhat consistent.
But sadly, no, it doesn’t.
Now, you may say. “Oh Zef, give whatever company produced this a chance. I’m sure it’s a version 1.0 fluke.” Sadly, this product has been around for over a decade.
No more excuses.