Discussions

Communicate with your team through project channels directly inside your code editor. Browse channels, send and receive messages, search conversations, and track unread counts.

The Problem This Solves

Developer communication is split across too many tools — Slack for chat, email for clients, browser for project-specific discussions. When a conversation is about a project task, it should live in the project context, not scattered across separate apps.

GitScrum Studio puts project discussions inside an editor panel. Ask a question about a task, share a code reference, or coordinate with a teammate — all from the same window where you write code.

What You Are Looking At

Click Discussions under the Knowledge section in the sidebar tree. The panel opens with a multi-panel layout:

Channel Sidebar

The left side lists all discussion channels for the active project. Each channel shows:

• Channel name — The topic or team the channel is for
• Unread count — Number of new messages since your last visit

A search field at the top lets you filter channels by name.

Messages Area

The center area displays messages in the selected channel. Messages show:

• Author name and avatar
• Message content
• Timestamp

Messages load with cursor-based pagination. Scroll up to load older messages, scroll down for newer ones.

Members Panel

The right side shows project members, providing context about who is in the conversation and available to respond.

Sending Messages

Type your message in the compose area at the bottom of the messages panel and press Enter or click Send. Messages appear immediately in the conversation.

Channel Management

Creating Channels

Create a new channel to organize discussions by topic, team, or feature. Provide a channel name and optional description.

Updating Channels

Edit channel details like name and description as project needs evolve.

Search

Use the search functionality to find specific messages within a channel. This is useful for finding past decisions, code references, or action items from previous conversations.

Unread Tracking

The channel sidebar shows unread counts for each channel. When you open a channel, its messages are automatically marked as read. This helps you quickly identify where new conversations are happening.

Pro Tips (Once You Are Comfortable)

• Create topic-specific channels. Instead of one general channel, create channels per feature, sprint, or module. This keeps conversations focused and searchable.

• Pin the Discussions panel. Keep it as a tab alongside your code. Glance at it between tasks to stay in sync with team conversations.

• Use unread counts as a quick health check. High unread counts on specific channels may indicate active design discussions or blockers you should weigh in on.

• Search before asking. Check previous messages before posting a question — someone may have already answered it.

Permissions

The extension respects your GitScrum account permissions:

• Agency Owners and Managers: Full access — create channels, send messages, manage members
• Developers: Can send messages and participate in channels for assigned projects
• Clients: Cannot access discussions

How to Report a Problem or Request a Feature

If messages fail to send, channels do not load, or unread counts are inaccurate, open a support ticket in the GitScrum web application. Navigate to Support Tickets in the sidebar and describe the issue. Include the extension version and editor details.