• frezik@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    12
    ·
    1 day ago

    GitHub tickets are fine.

    Jira is complicated because PMs want it to do everything. It can, but there’s no good reason for it.

    • AA5B@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      2 hours ago

      Yeah, jira is too customizable. I mean I wouldn’t give any of it up, but the one time someone let me have the reins, I mostly simplified. Removed workflows, removed customizations.

      There needs to be better ways of defining standard projects and sticking to them. Currently everyone wants their little tweak and you can’t even pick out what’s consistent and what’s not until you run into problems

    • qevlarr@lemmy.world
      link
      fedilink
      arrow-up
      19
      ·
      1 day ago

      just one more workflow bro. i promise bro just one more custom workflow and it’ll fix everything bro. bro, just one more scheme. please just one more, one more custom field and we can fix this whole project bro, bro cmon just give me one more automation rule i promise bro, bro bro please ! just need one more permission scheme bro please bro i can fix this i swear bro just one more post-function bro please

    • bleistift2@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 day ago

      The only thing GitHub can’t to is structure tickets. It would be nice to link issues together other than by referencing them.

    • laranis@lemmy.zip
      link
      fedilink
      arrow-up
      1
      ·
      1 day ago

      This. So fucking much this. I’ve seen Jira used to plan waterfall schedules, to track meeting actions, and as a relational database. And all of them claiming to be “agile”.

      When used for the right thing in the right way, Jira is a great tool. It is people who make it shitty, and specifically the type of PM who doesn’t understand the complexities, people or technical, of their work.