• Yote.zip@pawb.social
    link
    fedilink
    arrow-up
    28
    ·
    1 year ago

    I’m probably just bad at agile but I usually prefer if QA sends a quick message about a bug first to make sure it’s actually a bug and they’re not just misunderstanding a story.

    • toofarapart@lemmy.world
      link
      fedilink
      arrow-up
      19
      ·
      1 year ago

      That seems perfectly reasonable.

      What comes to mind when I see this meme is more along the lines of CS DMing devs directly with customer issues and expecting us to magically come up with a solution to something with minimal information given.

    • Dandroid@dandroid.app
      link
      fedilink
      arrow-up
      7
      ·
      edit-2
      1 year ago

      I love those because they close so quickly. Everyone gets X bugs per sprint, and I closed one in 30 minutes. One less thing to do this sprint.

    • Petri@sh.itjust.works
      link
      fedilink
      arrow-up
      5
      ·
      1 year ago

      Or it’s because every time they make a ticket it’s so messy it can’t be understood.

      Of course the grizzly way to respond back is to reassign it back to the QA and demand clarity and reproduction of the issue.

      • abraxas@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        That ain’t very grizzly. We have a “need more info” column in our support trello and nobody has a problem with it.

  • Shadow@lemmy.ca
    link
    fedilink
    arrow-up
    10
    ·
    1 year ago

    Jira plugin FTW.

    Right click their message - create a ticket from this message.

    • Petri@sh.itjust.works
      link
      fedilink
      arrow-up
      12
      ·
      1 year ago

      And then assign it back to them requesting they specify all the details so it can be groomed in the next scrum (hahah)

      • Restaldt@lemmy.world
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        And then you close the ticket and mark it as wont do because they dont know what they want and the details dont help

  • HiddenLayer5@lemmy.ml
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    And usually it’s your boss doing that so it’s not like you can just ignore it till they file a ticket.

    • abraxas@lemmy.ml
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      As a boss, if it’s not important enough for me to take the time to make a ticket, I’m not gonna get that mad at the pushback. But then, I’m in a small company so if it is important my response might be “I have another 7 hours of meetings ahead of me, could you pivot to getting replication and add a ticket, and then assign it to yourself?”

  • Koffiato@lemmy.ml
    link
    fedilink
    arrow-up
    4
    arrow-down
    1
    ·
    1 year ago

    Honestly that just shows bug report templates/rules are too hard for most users.

    • beepaboopa@lemmy.fmhy.ml
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Folks want to offboard their issue somewhere with minimal effort. It’s much easier to do that in free text in an app you’re already in than to submit a form where you have to categorize your issue on a website you’d have to pull it.

      You’re right to say it’s friction making people step outside the preferred path.

      People are lazy.

  • Chiyo@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Where I work, we send emails to users from their tickets. They are expected to reply to the emails, but sometimes they ignore the email and message us on Teams. If we give in and reply to their message, they tend to think they can message us for anything little thing. So then we become their personal IT guy. I’ve had to mute and hide people because they wouldn’t leave me alone. It’s like they don’t realize we are busy with other work. Go through the proper channels. Once you have a ticket, we will email you. IMing us is like trying to cut in line.