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
Search - "jira queue"
-
Last week my PM scheduled a meeting for the whole team of 14 devs to talk about our tasks, how we can improve our workflow, so he's up to date on daily stuff nad sprint progress. After an hour and a half of lots of brainstorming i just asked
- what exactly do you want to achieve with all these changes?
- basically i would like on overview of current progress on each task
And he proposed couple of different meetings during the sprint, which would waste dev time. He proposed to apoint one person reaponsible to keeping him informed during each sprint. He proposed we change our meetings, our process, all of it.
So I just sat with my laptop during the same meeting and I prepared a jira board with swimlanes, filters, etc. Where you can sort by priority, size, what is blocked, what is, waiting in queue, what is being currently developed, what is being tested, what's ready for deployment, etc. Easy. 5-10mins of work.
- does this solve your problem?
-....
- you have everything here
-... What if someone doesn't update the ticket status?
- we check everything during our dailies, so, worst case scenario is the status is not update for 24h
-... Umm.. Yeah.. I think thats it. Thank you.
So, we basically wasted 20+ man-hours on another bullshit meeting because the guy thats supposed to be using these tools doesn't know them at all. After working here for 6 months. -
JIRA queue just dropped into the single digits for the first time in weeks. It's getting me right in the feels.
-
Team Lead (not my team, thankfully) sends outs a team-wide message (in their exact words):
"please DM me with the task link if you are adding any new tasks in Jira. This is to make sure that i am aware of any ad-hoc task coming up in the jira queue and also to make sure that all the task are following a common template."
Interpretation : "I'm just too lazy to look at each jira issue after the last one that I followed up on (which is my job BTW). So I'll add some extra work for you to explain everything to me on DM"
Way to go for killing productivity. ¯\_(ツ)_/¯
Thankfully, this is not my team. If they were my team lead, I'd be super furious. I'd even report it to upper management. I'd even offer to do their job and let them do mine. I think their job just got so easy if everyone was to go report to him like that.3 -
Almost all of the issue trackers
Why can't any of them just decide to be good for one kind of process. Trying to fit in support for all of them just makes the products worse.
If you really want to cater to every style of issue tracking/work queue just make a low code platform from the start instead of the unholy mess that is jira1