Proposal Overview

I propose updating the default visual representation for generic Issues in the OneDev interface. Currently, generic issues utilize a "Bug" glyph (🐞), which creates semantic inconsistencies and imposes unnecessary negative framing on project workflows.

This change suggests replacing the existing icon with a standard Document icon, as defined below.

<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round">  
  <!-- Document body -->  
  <path d="M14 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V8z" />  
  <!-- Folded corner -->  
  <path d="M14 2v6h6" />  
  <!-- Content lines -->  
  <line x1="8" y1="13" x2="16" y2="13" />  
  <line x1="8" y1="17" x2="16" y2="17" />  
</svg>

🧠 Rationale & UX Motivation

1. Semantic Accuracy & Categorization Costs A "Bug" specifically denotes a defect or regression. However, the term "Issue" encompasses a broader taxonomy including feature requests, tasks, documentation updates, and discussions. Using a bug icon for all items creates a categorization mismatch. Users submitting feature requests are cognitively forced to reconcile their input with a symbol implying "error." This introduces friction and category ambiguity, increasing the cognitive load required to understand the nature of the workflow item.

2. Mitigating Negativity Bias & Affective Prediction Human decision-making is heavily influenced by Negativity Bias, where adverse stimuli evoke a stronger psychological reaction than neutral stimuli. A grid of bug icons unconsciously signals "failure," "instability," or "brokenness." When users look at a project board, seeing dozens of bug glyphs can subconsciously trigger anxiety or stress regarding the project's health. Replacing this with a neutral "Document" icon provides emotional neutrality—transforming the perception from "managing errors" to "processing tasks," which promotes psychological safety and productivity.

3. Universal Affordance & Visual Hierarchy From a semiotic perspective, a document icon acts as a universal container. It implies structure, storage, and distinct units of work without prescribing content type or quality status. It creates a cleaner, more professional visual hierarchy, allowing the issue title and priority flags to do the heavy lifting regarding context, rather than relying on a potentially misleading pictograph.

Expected Outcome

By decoupling the generic "Issue" state from the specific "Defect" symbol, we improve the usability and perceived value of the OneDev system. It aligns the visual language with standard industry practices where "Issue" represents a ticket for action, regardless of whether the action is fixing a leak or building a new wing.