For development shops
Your developers work in Gitea. Your clients work here. It is the same task.
Picture a web shop: five developers, thirty clients, and every client sure that theirs is the only site you build. The client writes "the header is wrong on my phone" in plain words. The developer sees an issue in the repository, with the branch and the pull request beside it. Nobody typed it twice, and no client will ever read a stack trace.
The client has a room of their own
One project per client, and the client is a guest in it: they see their own work and nobody else's, read everything, and write notes. Your developers see every project. A late task shows the client the same red the developer sees.
The task becomes the issue
Connect the project to its repository and choose which tasks cross: all of them, or only those with a label such as dev. Each one opens an issue titled with the task's reference, carrying the description and a link back. Marking it done closes the issue; in progress and blocked are labels on it.
The client's note lands on the issue
When the client adds a note, it becomes a comment on the issue with their name on it, so the developer reads what the client actually said. The developer's comments stay in the repository. Nothing comes back into sjTasks yet; the issue does not close the task.
And the rest of the shop
The project's news can go to a Slack channel, and a task can be made from that channel with a single line. A client who prefers email replies to the notice and the reply is a note on the task. Every night, whoever wants it gets one email with what is late, what is due, and what changed. All of it is on every plan.
The five-step path A developer shop and its clients sets this up in an afternoon. What each connection carries is on the integrations page.
Start for free No card. Guests are free on every plan.