• musicmatze@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    2 years ago

    You don’t seem to be a developer :)

    I have been a developer for over 10 years now.

    If you mix them with general discussions your entire project cycle management system breaks as you can’t have clear milestones etc. with forever open “issues” that are not issues but discussions.

    I don’t see why an issue must be assigned to a milestone, so I don’t see how an issue can break any lifecycle.

    • smallcircles@lemmy.mlOPM
      link
      fedilink
      arrow-up
      1
      ·
      2 years ago

      How an issue is used in a development project is “it depends”. Whatever the chosen and preferred method of the maintainers is. If you really want a concise backlog with concrete stuff, and no “pie in the sky” musings on future major extensions, then Discussion section can be very handy. If you don’t use discussions, you may end in a situation where off-topic’ish issues sit in the backlog like forever, and pile up.