A busy service request collects two kinds of comments. Some are for the customer. Others are agents talking it through: “Did security approve this?” “I think this is the same as last week’s request.” Jira Service Management has internal notes, but on a long request they all sit in one flat list. Finding the answer to a question means scrolling through everything else.
What a thread changes
AppsDelivered Comments adds threaded comments to Jira. You reply to a comment, and the reply sits under it. Someone replies to the reply, and it nests again. A request with three open questions has three threads, each with its own answer.
In Jira Service Management spaces, you can also start an internal thread. Agents discuss the request in the thread, and the customer never sees it. The discussion stays on the request, next to the work, instead of in a chat channel that nobody can find later.
When to use an internal thread
- Approvals. Ask the approver in a thread, and keep their answer under the question.
- Handoffs. When a request moves to another team, leave a handoff note as a thread, and let the next team ask follow-up questions under it.
- Investigations. Keep notes from each person who looked at the problem in one place.
Pair it with comment templates
Threads work well with comment templates. A “Handoff note” template gives every handoff the same shape: what the customer asked, what we tried, what is left. The next agent knows where to look.
Permissions stay the same
Threaded comments use Jira’s own permissions. If someone can’t see a request, they can’t see its threads. Comment templates add their own permission settings, so you decide who can create and use them.
Long requests will always exist. Threads make them readable.



