Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@SortOfTested thats the way to go.
-
@SortOfTested That's wanting the world to burn.
-
Was the process agreed upon?
If not than the can do whatever they want until you make @soulevans07's point happen.
If was accepted just ignore the crap they spout you. If it isn't in the system it wasn't requested. If they break a promise and make your life miserable. Don't reward them for it reward the ones that do it properly and celebrate the great working result. It's like puppy training... -
Just refuse to work without proper tickets. Change to pulling tickets instead of pushing them to devs helps a lot too as it has to be specified otherwise they always get tickets back as "refused as spec is missing". Best way is to don't allow assigning tickets to devs directly. They can't skip steps if they don't know who will be working on the ticket
-
@ShotgunSurgeon thats a great idea. I will talk with the other devs about this idea. Thank man 😊
Can someone relate to it? We have a very simple process:
1. Create a ticket 🎫
2. Specify the requirement 📑
3. Assign the ticket to a developer 👨🦰👩🦰
4. Optional: make a meeting with the developer and go throw the specification if it is a complex feature 🗓️
Under pressure it looks like this:
Someone tells you to implement the request as fast a possible, no written specification, in best case you get a brief email 📧 also the feature has to be available asap in production and they is only poorly tested...
Or they want to test in production because the data in test system is "missing" ⛔☢️☣️
It is so annoying that is so difficult to stick to such a simple process 😭 it really freaks me out 😒😫
rant
fdd
workday
ticket
workhell