I have a lot of trouble ticket assigned to me. We release them to the customer in batches. The development cycle is usually about a month long for each. We have a trouble ticketing system. In that system, each ticket gets assigned to a release. Many of my tickets were not assigned to releases. There are only two future released currently planned.
The big boss said all tickets must get a release assigned in the ticketing system. Okay. I went through and just assigned everything to the next release. Check. But I wonder what they are using that release for? I bet this is used to convey expected resolution times to the customer. Oops.
Realistically there are only a few tickets that I am going to resolve in the next release. I already know that. I don’t get to spend all my time working this new release. I have to support the previous release in all the stages of testing it goes through. I am also taking a vacation next month. All this adds up to some unpleasant surprises come delivery time.
I need to make sure I am not part of the problem. Time to stand up and raise the alarm about this release issue. My team lead said I should just leave the release dates blank, forcing everyone to deal with the underlying issue. That is all good and dandy, but I am tired of getting beat up because my tickets don’t have release dates set.
