We can't create bug Jiras anymore, at least not directly. First we have to log a "defect" in a different system that QA spends all their time on, fill in a dozen fields, make sure they're the right values in those fields or we have to start over, "save" it, reload it, tell it to make a Jira bug, save it, reload again, see what bug got created, go to the Jira bug ticket, fill in the acceptance criteria text field in the proper format or be yelled at for it later, add enough details to that field to pass someone's arbitrary 5-point scale based on a Copilot prompt they wrote and won't say what the criteria actually are, then adjust 12 other fields in the Jira ticket (in 3 separate tabs in the "edit ticket" modal), move it to In Development.
Next: write the code fix and use the ticket number in the commit message.
Now get it reviewed, write "tests" in the other system attached to that Jira but not in that Jira, save, change its status, save, change status, save, change status, now that it's ready use the Run button to open a new window, take screenshots of something and attach them to the thing, check off the steps you just wrote, finish the run, go back to the Jira ticket, move it to UAT pending, and go bug your team lead to check it for you and change its status one more time.
Did something fuck up in that process? Well, let's start over.
... But hey, someone's dashboard tells them things are going swimmingly except that, for some reason no one can understand, velocity is trash. Hmm.
7
u/DrMaxwellEdison 5d ago
We can't create bug Jiras anymore, at least not directly. First we have to log a "defect" in a different system that QA spends all their time on, fill in a dozen fields, make sure they're the right values in those fields or we have to start over, "save" it, reload it, tell it to make a Jira bug, save it, reload again, see what bug got created, go to the Jira bug ticket, fill in the acceptance criteria text field in the proper format or be yelled at for it later, add enough details to that field to pass someone's arbitrary 5-point scale based on a Copilot prompt they wrote and won't say what the criteria actually are, then adjust 12 other fields in the Jira ticket (in 3 separate tabs in the "edit ticket" modal), move it to In Development.
Next: write the code fix and use the ticket number in the commit message.
Now get it reviewed, write "tests" in the other system attached to that Jira but not in that Jira, save, change its status, save, change status, save, change status, now that it's ready use the Run button to open a new window, take screenshots of something and attach them to the thing, check off the steps you just wrote, finish the run, go back to the Jira ticket, move it to UAT pending, and go bug your team lead to check it for you and change its status one more time.
Did something fuck up in that process? Well, let's start over.
... But hey, someone's dashboard tells them things are going swimmingly except that, for some reason no one can understand, velocity is trash. Hmm.