Tasks is the most finite of git building blocks. Example tasks: “Clean up CI/CD”, “merge PR”. I think in Linear task most closely maps to “sub-issue”. Issues are a step above that can be used to describe bug reports, user stories. Milestones are collections of issues.

Yeah lol, not talking about Git tasks indeed :winkwithtongue:

Tasks (can) have sub-tasks. So then I still see Issues as a type of Task. And I don't want to embed an Issue into a Task (in my Community / Team group), when they' the same thing.

Would be curious in general how you would re-imagine the product management event stack. Without the silos that force imo more copy-pasting / embedding and levels then is needed. Blank canvas in an interop world. What do you minimally need?

open source developers do not want tasks

Fine if we call 'em "issues" then? Same for me.

My designs / widgets for both look :90percent: the same. That's why I'm asking.

I introduced the idea of tasks mostly as a generic thing, for task-tracking applications that are not git-specific. However, I also imagined that there are people using NIP-34 issues already, and that they might want to track them in a workflow. So in the "XXD" draft, I introduce workflows that can track any nostr kind, including git issues and more generic tasks. The intent was to keep compatibility with NIP-34, but also provide a more generic task type for non-git applications.