3 ms·

First time I used Jira I was lucky that the company had it setup quite nicely. I really enjoyed it. One of the things I really enjoy about Jira is the fact th

• lloeki 3y ago
  "Hey this PROJ-1234 task is in fact a subtask of PROJ-1111!" "Agreed! let's move it to be a subtask of PROJ-1111! and here's a new PROJ-1235 for the second part, let's make it a subtask as well" "Wait, I can't make PROJ-1234 a subtask of PROJ-1111..." "Ah, I see, PROJ-1111 is already a subtask of PROJ-1002, which indeed makes sense" "Oh, right! I forgot subtasks can't be nested. So maybe PROJ-1002 is an epic?" "Sounds about right! Oh wait, PROJ-1002 is part of epic PROJ-223" "Oh. I get it now, forgot about that epic which tracks things for product item foo" "Alright, is foo still on track and required?" "Yeah, it's merely been postponed because the currently worked on project item bar was priorised as we needed a bit more work to refactor and complete foo" "So now we're set to do PROJ-1234 in the current sprint, and this would complete both foo and bar, two birds one stone!" "Yeah that was the plan all along, having the design lend itself to that, with proper composition and all." "But we can't make it part of both epics" "Correct." "What if we create a new task and link it with PROJ-1234" "Could work. How do we qualify it though? It's "duplicated by" but we keep that for duplicate bug reports as there are automated workflows for it, notably a duplicate is supposed to be closed." "Blocked by maybe?" "Well it's kind of bidirectional and blocked by is one direction only" "Drat there's no "Linked to" in the combo box" "Yeah management wants everything qualified so that they can build reports. IIRC they don't scope it by kind "bug" because marking some tasks as bugs biases another counter, so some bugs stay as tasks, so they can count only bugs reported by customers and not internal bugs" "Oh right, doubles down on why we can't use duplicate, we'd break the report. Actually I think we can't use the link feature at all because it's really the same task and that'd break their report too" "Screw it let's just put a link on each one's description to the other. I'll shoot an email to the JIRA admin to see if we can add more link kinds, and maybe fix the automations and reports" "Yeah, we're already overtime for that sprint planning anyway. Let's move." "Should we do that at the PROJ-1234 level or at the PROJ-1111 level?" "Not too sure. Maybe we should have used a checklist for PROJ-1111" "But then PROJ-1478 depends on PROJ-1234 only, not PROJ-1111 as a whole" "Ah, right. Maybe we cleaned up the arch a bit too much lol" "Right? Maybe we should switch to an arch that matches how we can link tickets lolsob" "JDD: JIRA driven development" "Hold my beer while I write a JIRA plugin to export task structure as a code scaffold" "Kill me right now" "Goddammit time flies, let's finish this. So where are we on PROJ-1526?" "Blocked, we're waiting on feedback from the user" "Alright. Wait, there are two "Waiting on customer" statuses now? Which one is it?" "Huh. Let me look at the browser inspector... Ok, id 17, so I think it's the second one. No idea where the other one comes from." "Ha. Ok, moving on." Slack pings > Hey, meeting xyz has started 10min ago, are you joining? "Drat"
  • bentobean 3y ago
    It’s funny because it’s true.