Preferences

All those users are why bug trackers are annoying. I don't care about those fields "those other people" are demanding, why do I need to fill them out. Mean while they don't care about the fields that are critical for me and don't want to fill them out.

pixl97
There's no I in team...

Or to put it another way, those other 'useless' fields that take minutes may save the company hours of time in places that you don't see.

account42
More like they justify some middle management busybody's salary.
MonkeyClub
> There's no I in team...

But there's U and I in unity!

/s aside, you have a valid point there: just because "I" find the field useless, it doesn't mean that it isn't out to actual good use downstream.

Every job has a part people don't like that's necessary. The company you work for pays you money to fill the fields out, you fill them out, you get paid.
XorNot
That's why I do it. That doesn't explain why they even need to be there.

For example every project code drop down has this experience: my manager tells me what project code to put everything against, then I always pick the same option. Sometimes I've not been granted access to that option and waste a bunch of time getting that turned on.

At no point was any part of this necessary, because I neither defined the ticket, or could select the project code for myself, but we're all engaged in an elaborate game pretending I had agency over it.

AndrewDucker
If you're working somewhere competent then every budget code is an indicator that a manager with a budget has said that they are willing to pay for this piece of work to be done. It may even automatically keep track of how much of their budget was spent on you doing the work.
account42
Or you could show initiative and improve inefficient processes instead of blindly following "how things are done".

This item has no comments currently.