Elixion

Creating Issues

Learn how to create and configure issues effectively in Elixion

Creating Issues

This guide covers all the ways to create issues in Elixion and how to configure them properly for effective tracking.

Quick Create

From Anywhere

Press Ctrl/Cmd + I to open the quick create modal:

  1. Enter title
  2. Select project
  3. Choose type (optional)
  4. Press Enter to create

The issue is created with defaults; edit it later to add details.

From the Board

Click + New at the top of any column:

  1. Enter title
  2. Issue is created in that column's status
  3. Click the issue to add details

From Project List

  1. Navigate to project
  2. Click + New Issue
  3. Fill in the creation form

Full Creation Form

Basic Information

Title (Required)

  • Clear, descriptive summary
  • 3-200 characters
  • Start with action verb for tasks

Examples:

Good: "Implement user authentication with OAuth2"
Good: "Fix: Login button unresponsive on Safari"
Bad:  "Auth stuff"
Bad:  "Bug"

Description Use markdown for rich formatting:

## Context
Brief background on why this is needed.

## Requirements
- Requirement 1
- Requirement 2

## Acceptance Criteria
- [ ] Criteria 1
- [ ] Criteria 2

## Technical Notes
Any implementation details.

Issue Type

Select the appropriate type:

| Type | When to Use | |------|-------------| | Epic | Multi-sprint feature | | Story | User-facing functionality | | Task | Technical work item | | Bug | Defect report | | Tech Debt | Technical improvement | | Spike | Research/investigation |

Project

Select which project this issue belongs to. This determines:

  • Issue key prefix
  • Available workflows
  • Team members who can see it
  • Custom fields available

Status

Default is "Open" but you can set initial status:

  • Open (default)
  • In Progress (start work immediately)
  • Backlog (not for current sprint)

Priority

Set urgency level:

  • Critical - Immediate attention
  • High - Address soon
  • Medium - Normal priority (default)
  • Low - When time permits

Assignment

Assignee

  • Leave empty for backlog items
  • Assign to self to start immediately
  • Assign to team member

Watchers Add users to receive notifications:

  • Reporter is auto-added
  • Assignee is auto-added
  • Add additional watchers manually

Planning

Sprint

  • Leave empty for backlog
  • Assign to active sprint
  • Assign to future sprint

Story Points Estimate effort:

  • Use Fibonacci: 1, 2, 3, 5, 8, 13, 21
  • Relative sizing, not hours
  • Leave empty if not estimated

Due Date Set deadline if applicable:

  • Soft deadline (target)
  • Hard deadline (commitment)
  • Leave empty if flexible

Organization

Epic Link to parent epic:

  • Search by title or key
  • Creates parent-child relationship
  • Contributes to epic progress

Labels Add categorical tags:

  • Select from existing labels
  • Create new labels inline
  • Multiple labels allowed

Components Mark affected components:

  • Frontend
  • Backend
  • Database
  • API
  • (Custom components)

Attachments

Add files to the issue:

  • Drag and drop
  • Click to browse
  • Paste from clipboard

Supported types:

  • Images (PNG, JPG, GIF)
  • Documents (PDF, DOC, TXT)
  • Archives (ZIP)
  • Max 10MB per file

Creating Specific Types

Creating a Bug

Include these details:

## Bug Description
What is happening incorrectly?

## Steps to Reproduce
1. Go to [page]
2. Click [element]
3. Observe [error]

## Expected Behavior
What should happen instead?

## Actual Behavior
What is actually happening?

## Environment
- Browser: Chrome 120
- OS: macOS 14.1
- Device: MacBook Pro

## Screenshots/Logs
[Attach screenshots or relevant logs]

Required fields:

  • Severity (Critical, Major, Minor, Trivial)
  • Affected version
  • Environment details

Creating a Story

Use the story format:

## User Story
As a [type of user],
I want [feature/capability],
so that [benefit/reason].

## Acceptance Criteria
- [ ] When I [action], [expected result]
- [ ] Given [context], when [action], then [result]
- [ ] The feature should [requirement]

## Design
[Link to designs if available]

## Technical Considerations
[Any technical constraints or notes]

Creating an Epic

Epic description template:

## Overview
High-level description of this epic.

## Goals
- Goal 1
- Goal 2

## Success Metrics
How will we measure success?

## Scope
### In Scope
- Feature A
- Feature B

### Out of Scope
- Feature C (future consideration)

## Timeline
Target: Q1 2024

## Child Issues
Issues will be linked as children.

Creating a Spike

Spike template:

## Research Question
What are we trying to learn?

## Background
Why do we need this research?

## Time Box
Maximum: 2 days

## Expected Output
- Document with findings
- Recommendation for next steps
- Estimated effort for implementation

## Resources
- [Link to relevant docs]
- [Link to similar implementations]

Bulk Creation

Import from CSV

  1. Go to Project > Import > CSV
  2. Prepare CSV with columns: 
    Title,Type,Priority,Description,Labels
"Fix login bug",Bug,High,"Steps to reproduce...",bug,urgent
"Add search",Story,Medium,"As a user...","feature,search"
  3. Upload and map columns
  4. Preview and import

Clone Existing Issue

  1. Open issue to clone
  2. Click ⋮ More > Clone
  3. Choose what to copy:
    • ☑ Description
    • ☑ Labels
    • ☐ Attachments
    • ☐ Comments
    • ☐ Subtasks
  4. Modify and create

Create from Template

  1. Click + New Issue
  2. Select From Template
  3. Choose template
  4. Fill in placeholders
  5. Create

After Creation

Verify Details

  • Check all fields are correct
  • Ensure proper categorization
  • Verify assignee is appropriate

Link Related Items

  • Connect to parent epic
  • Link blocking/blocked issues
  • Associate GitHub PRs

Notify Team

  • Issue watchers are notified
  • Share in team channel if needed
  • Discuss in standup if urgent

Next: Issue Types - Deep dive into different issue types