Plan

Observations

The issue timeline displays system-generated events (stored as issueComments with isSystem: true) alongside regular comments. Currently, when an issue is created, a redundant "Issue reported by..." system event is added to the timeline, even though the initial issue post already shows this information. Additionally, system events display "System" as the author name in the UI, which adds unnecessary visual clutter.

Approach

The refactoring involves two main changes: (1) Remove the creation of the "Issue reported by..." system event in the createIssue function, and (2) Remove the "System" label from the timeline rendering by not displaying the author name for system events. This approach maintains the visual distinction of system events (small dot vs avatar) while cleaning up redundant information and labels.

Implementation Steps

1. Remove "Issue created" System Event

File: file:src/services/issues.ts

In the createIssue function (lines 85-209), remove the timeline event creation:

Delete lines 136-142 that create the "Issue reported by..." timeline event
Remove the reporterDesc variable calculation (lines 136-137)
Remove the createTimelineEvent call (lines 138-142)

2. Remove "System" Label from Timeline UI

File: file:src/components/issues/IssueTimeline.tsx

In the TimelineItem component (lines 30-122), modify the system event rendering:

In the system event rendering block (lines 53-69), remove the author name display
Delete lines 55-60 that display event.author.name with the "System" label
Keep the content and timestamp display (lines 61-68)
The visual structure should show: {content} • {timestamp} without the author prefix

Alternatively, in the comment normalization section (lines 159-172), you can stop setting a default "System" author name since it won't be displayed anymore.

3. Update Unit Tests

File: file:src/services/issues.test.ts

In the createIssue test (lines 122-162):

Remove or update line 146 that verifies createTimelineEvent was called
The test should no longer expect a timeline event to be created during issue creation

4. Update Integration Tests

File: file:src/test/integration/supabase/issue-services.test.ts

In the "createIssue with reporter variations" describe block (lines 217-303):

Remove or update the assertions that check for "Issue reported by..." timeline events
Specifically update:
- Lines 242-248 (guest reporter test)
- Lines 271-274 (anonymous reporter test)
- Lines 298-301 (member reporter test)
These tests should no longer expect to find system events with "Issue reported by" content

5. Update E2E Tests

File: file:e2e/smoke/reporter-variations.spec.ts

Remove or update the following assertions that check for "Issue reported by..." text:

Line 44: Remove await expect(page.getByText("Issue reported by John Guest")).toBeVisible();
Line 49: Remove await expect(page.getByText("Issue reported by Only Name")).toBeVisible();
Lines 59-61: Remove the assertion for "Issue reported by only@email.com"
Line 72: Remove await expect(page.getByText("Issue reported by Guest")).toBeVisible();

These tests should focus on verifying the reporter information in the sidebar and the initial issue post, not in a separate system event.

6. Verify Other System Events Still Work

Ensure that other system events (status changes, assignments, severity/priority/consistency changes) continue to display correctly in the timeline. These should still show their content and timestamp, just without the "System" prefix.

Visual Changes

sequenceDiagram
    participant User
    participant CreateIssue as createIssue()
    participant Timeline as IssueTimeline
    participant UI as Browser

    User->>CreateIssue: Submit new issue
    CreateIssue->>CreateIssue: Insert issue record
    Note over CreateIssue: ❌ Remove: createTimelineEvent("Issue reported by...")
    CreateIssue->>Timeline: Return issue data
    Timeline->>Timeline: Normalize events
    Note over Timeline: Issue event (type: "issue")<br/>Comments (type: "comment")<br/>System events (type: "system")
    Timeline->>UI: Render timeline
    Note over UI: Issue card shows reporter info<br/>System events show: content • timestamp<br/>❌ Remove: "System" label

Testing Checklist

After implementation, verify:

Issue creation no longer generates a "Issue reported by..." system event in the database
Timeline displays the initial issue post with reporter information
System events (status, assignment, severity, priority, consistency changes) still appear in timeline
System events display only content and timestamp, without "System" prefix
All unit tests pass
All integration tests pass
All E2E tests pass

Import In IDE

🤖 Prompt for AI Agents

## Observations

The issue timeline displays system-generated events (stored as `issueComments` with `isSystem: true`) alongside regular comments. Currently, when an issue is created, a redundant "Issue reported by..." system event is added to the timeline, even though the initial issue post already shows this information. Additionally, system events display "System" as the author name in the UI, which adds unnecessary visual clutter.

## Approach

The refactoring involves two main changes: (1) Remove the creation of the "Issue reported by..." system event in the `createIssue` function, and (2) Remove the "System" label from the timeline rendering by not displaying the author name for system events. This approach maintains the visual distinction of system events (small dot vs avatar) while cleaning up redundant information and labels.

## Implementation Steps

### 1. Remove "Issue created" System Event

**File: `file:src/services/issues.ts`**

In the `createIssue` function (lines 85-209), remove the timeline event creation:
- Delete lines 136-142 that create the "Issue reported by..." timeline event
- Remove the `reporterDesc` variable calculation (lines 136-137)
- Remove the `createTimelineEvent` call (lines 138-142)

### 2. Remove "System" Label from Timeline UI

**File: `file:src/components/issues/IssueTimeline.tsx`**

In the `TimelineItem` component (lines 30-122), modify the system event rendering:
- In the system event rendering block (lines 53-69), remove the author name display
- Delete lines 55-60 that display `event.author.name` with the "System" label
- Keep the content and timestamp display (lines 61-68)
- The visual structure should show: `{content} • {timestamp}` without the author prefix

Alternatively, in the comment normalization section (lines 159-172), you can stop setting a default "System" author name since it won't be displayed anymore.

### 3. Update Unit Tests

**File: `file:src/services/issues.test.ts`**

In the `createIssue` test (lines 122-162):
- Remove or update line 146 that verifies `createTimelineEvent` was called
- The test should no longer expect a timeline event to be created during issue creation

### 4. Update Integration Tests

**File: `file:src/test/integration/supabase/issue-services.test.ts`**

In the "createIssue with reporter variations" describe block (lines 217-303):
- Remove or update the assertions that check for "Issue reported by..." timeline events
- Specifically update:
  - Lines 242-248 (guest reporter test)
  - Lines 271-274 (anonymous reporter test)
  - Lines 298-301 (member reporter test)
- These tests should no longer expect to find system events with "Issue reported by" content

### 5. Update E2E Tests

**File: `file:e2e/smoke/reporter-variations.spec.ts`**

Remove or update the following assertions that check for "Issue reported by..." text:
- Line 44: Remove `await expect(page.getByText("Issue reported by John Guest")).toBeVisible();`
- Line 49: Remove `await expect(page.getByText("Issue reported by Only Name")).toBeVisible();`
- Lines 59-61: Remove the assertion for "Issue reported by only@email.com"
- Line 72: Remove `await expect(page.getByText("Issue reported by Guest")).toBeVisible();`

These tests should focus on verifying the reporter information in the sidebar and the initial issue post, not in a separate system event.

### 6. Verify Other System Events Still Work

Ensure that other system events (status changes, assignments, severity/priority/consistency changes) continue to display correctly in the timeline. These should still show their content and timestamp, just without the "System" prefix.

## Visual Changes

```mermaid
sequenceDiagram
    participant User
    participant CreateIssue as createIssue()
    participant Timeline as IssueTimeline
    participant UI as Browser

    User->>CreateIssue: Submit new issue
    CreateIssue->>CreateIssue: Insert issue record
    Note over CreateIssue: ❌ Remove: createTimelineEvent("Issue reported by...")
    CreateIssue->>Timeline: Return issue data
    Timeline->>Timeline: Normalize events
    Note over Timeline: Issue event (type: "issue")<br/>Comments (type: "comment")<br/>System events (type: "system")
    Timeline->>UI: Render timeline
    Note over UI: Issue card shows reporter info<br/>System events show: content • timestamp<br/>❌ Remove: "System" label
```

## Testing Checklist

After implementation, verify:
- Issue creation no longer generates a "Issue reported by..." system event in the database
- Timeline displays the initial issue post with reporter information
- System events (status, assignment, severity, priority, consistency changes) still appear in timeline
- System events display only content and timestamp, without "System" prefix
- All unit tests pass
- All integration tests pass
- All E2E tests pass

Execution Information

Branch: main
Commit: 0d73d29

💡 Tips

Supported Commands (Inside Comments)

Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

Join our Discord Community to get help, request features, and share feedback.
Follow us on X/Twitter for updates and announcements.

Cleanup System Messages in Issue Timeline #763

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions