You could always try to convince everyone else to use org within a git repo. I'm serious: a decentralised VC system with structured text files is basically the centralised-project-tool killer.
And it's free. And it means everyone using emacs!
So, in case you were serious: there are good reasons to use more visual and collaborative tools in a team, one is that people won’t learn emacs just to be able to work with others and I personally don’t really care what editors my coworkers use, another reason is that non-engineers are also part of the team, and another one is that JIRA/Trello/etc support integration in others tools (GitHub, Slack, etc.).
I was semi-serious, semi-joking about how wonderful it'd be for everyone on a team to use emacs. It really is the best editor in existence, and it really is usable by anyone, not just developers. And it integrates with git[0], GitHub[1], Slack[2] &c. too!
EDIT: I also have been using it for documentation. Github parses orgmode files, so its useful for me and the rest of me team in these cases.
Not sure how that could be improved without adding a lot of complexity :(