Yes, an issue IS a Task, just more specifically tied to the repo, so basically the same format is applied. The problem would be that in some context you need to display *only* repo-issues related to the technical stuff, and other times you want to display only the broader project related stuff like tasks regarding marketing and promotion.

If you have the same kind for those, you're in trouble distinguishing between the two and are using much more resources than necessary.

Otherwise UI is mostly identical for them