Solution

Custom Fields 2026 | Severity, Story Points, Your Data

Generic tools: Title, Description, Status. No story points, no severity. Create custom fields: dropdown, number, checkbox. Filter, report, your data. Free trial.

Also on

Custom Fields 2026 | Severity, Story Points, Your Data

The One-Size-Fits-None Problem Every PM tool ships with: - Title - Description - Status - Assignee - Due date - Maybe priority That's it.

But your team tracks: For bugs: - Severity (Critical/Major/Minor/Trivial) - Affected version - Environment (Prod/Staging/Dev) - Steps to reproduce - Customer impact For features: - Story points - Business value - Risk level - Dependencies - Tech stack affected For tech debt: - Debt category - Interest rate (how fast it compounds) - Payoff estimate - Related systems Generic fields can't capture this. The Workaround Hell Teams without custom fields: 'Put story points in brackets in the title' Result: '[3] Implement OAuth [High Risk]' Unreadable.

Unparseable. Unreportable.

'Use labels for everything' Result: 47 labels. No structure.

Chaos. 'Add it to description' Result: Inconsistent.

Can't filter. Can't report.

'Use comments' Result: Lost in thread. Never found again.

Workarounds that fight the tool. Why Custom Fields Matter for Dev Teams 1.

Estimation and Planning Story points: - Not a standard field - Critical for velocity - Need to sum, average, filter Without custom field: - Manual tracking in spreadsheet - Velocity calculated by hand - Sprint planning guesswork 2. Bug Triage Severity vs Priority: - Severity: How bad is it?

- Priority: When do we fix it? - Different concepts, both needed Without custom fields: - Conflate into single 'priority' - Lose nuance - Wrong decisions 3.

Environment Tracking Where does this bug occur? - Production only - All environments - Staging specific Without custom field: - Buried in description - Can't filter bugs by environment - Time wasted reproducing 4.

Technical Metadata Every task might need: - Affected component - Tech stack (Frontend/Backend/Infra) - Database impact (Yes/No) - Breaking change (Yes/No) Without custom fields: - Information scattered - Architecture decisions uninformed - Tech lead can't get overview GitScrum: Create What You Need Custom field types: - Text (single line, multi-line) - Number (integers, decimals) - Dropdown (single select) - Multi-select (tags) - Date - Checkbox - User (assignee-type) - URL Create fields specific to your workflow. Example: Bug Tracking Setup Create fields: 1.

Severity (dropdown): Critical, Major, Minor, Trivial 2. Environment (dropdown): Production, Staging, Development 3.

Affected Version (text): Free-form version string 4. Customer Impact (number): Estimated users affected 5.

Regression (checkbox): Is this a regression? Now every bug has structured, queryable data.

Example: Sprint Planning Setup Create fields: 1. Story Points (number): Fibonacci scale 2.

Business Value (dropdown): High, Medium, Low 3. Risk Level (dropdown): High, Medium, Low 4.

T-Shirt Size (dropdown): XS, S, M, L, XL 5. Sprint Ready (checkbox): All criteria met?

Velocity calculated automatically. Sprint capacity visible.

Planning data-driven. Filtering by Custom Fields Real queries: - 'Show all Critical bugs in Production' - 'Show tasks with Story Points > 5' - 'Show features marked High Risk' - 'Show tech debt with High Interest' Filter.

Your data, your views. Reporting on Custom Data With structured custom fields: 'Average story points per sprint' → Automatic 'Bugs by severity distribution' → One click 'Time spent on tech debt vs features' → Report ready 'Tasks by risk level' → Instant filter No manual aggregation.

No spreadsheet exports. Project-Specific Fields Different projects, different needs: Project A (SaaS product): - Customer tier affected - API version - Billing impact Project B (Agency client work): - Client approval status - Billable (yes/no) - Change request (yes/no) Project C (Internal tools): - Department affected - Training required - Documentation status Customize per project.

Share templates across similar projects. Required vs Optional Fields Make critical fields required: - Story Points: Required (can't estimate without) - Environment: Required for bugs - Client Approval: Required before deploy Make others optional: - Notes: Nice to have - Risk Level: When applicable Enforce data quality.

Don't over-engineer. Default Values Set sensible defaults: - Severity: Medium (not Critical unless proven) - Environment: Production (assume worst) - Sprint Ready: Unchecked (until confirmed) Less friction on task creation.

Correct assumptions baked in. Vs Other Tools Jira: Custom fields exist but complex.

Admin-only creation. Field schemes confusing.

Performance degrades with many fields. Asana: Custom fields available on Premium+.

Limited types. Less flexibility.

Trello: Custom fields via Power-Up. Limited functionality.

Costs extra. Linear: Labels only.

No true custom fields. Limited structure.

GitScrum: Custom fields included. All field types.

Easy creation. Performance maintained.

Migration Friendly Moving from another tool? If source had custom fields: - Map to GitScrum fields - Import with structure intact If using workarounds: - Parse from titles/descriptions - Convert to proper fields - Clean data, better going forward

The GitScrum Advantage

One unified platform to eliminate context switching and recover productive hours.

problem.identify()

The Problem

Generic fields only - Title, description, status. No structure for your specific tracking needs.

Workaround culture - Story points in brackets. Labels for everything. Information buried in descriptions.

No structured queries - Can't filter by severity. Can't sort by story points. Can't group by environment.

Manual reporting - Export to spreadsheet. Aggregate by hand. Outdated before you finish.

One process fits all - Your bugs need different fields than features. Tool doesn't care.

Data quality chaos - Inconsistent entry. Missing information. No enforcement.

solution.implement()

The Solution

Full custom field types - Text, number, dropdown, multi-select, date, checkbox, user, URL. Build what you need.

Structured data capture - Every task has queryable fields. No workarounds. Real data structure.

Filter and sort - Query by any field. Show Critical Production bugs. Sort by story points. Group by risk.

Automatic reporting - Sum story points. Average cycle time. Group by custom fields. All automatic.

Project-specific fields - Different projects, different fields. Bug trackers vs feature planning. Customize each.

Required fields option - Enforce data quality. Required fields on creation. Defaults for common values.

workflow.steps()

How It Works

Define Field

Choose type (dropdown, number, etc.). Name it. Add options if needed. Set required or optional.

Apply to Tasks

Field appears on task forms. Fill in when creating. Update anytime. Structured data captured.

Filter and Sort

Use custom fields in filters. Show Critical bugs only. Sort by story points. Group views.

Report and Analyze

Generate reports using custom field data. Aggregate, average, distribute. Insights from your data.

expertise.verify()

Why GitScrum

GitScrum addresses Custom Fields for Development Tracking - Your Data Structure, Your Way through Kanban boards with WIP limits, sprint planning, and workflow visualization

Methodology

Problem resolution based on Kanban Method (David Anderson) for flow optimization and Scrum Guide (Schwaber and Sutherland) for iterative improvement

Capabilities

Kanban boards with WIP limits to prevent overload
Sprint planning with burndown charts for predictable delivery
Workload views for capacity management
Wiki for process documentation
Discussions for async collaboration
Reports for bottleneck identification

Industry Practices

Kanban MethodScrum FrameworkFlow OptimizationContinuous Improvement

features.related()

Related Features

View all features

Kanban Boards

Visualize by custom fields - Group cards by severity. Color by priority. Filter board by any field.

Sprint Planning

Sprint planning with data - Story points field enables velocity tracking. Capacity planning with real numbers.

Time Tracking

Time by custom field - Report time spent by severity, by component, by any custom dimension.

Git Integrations

Code and project management finally speak the same language. Connect GitHub, GitLab, or Bitbucket in two clicks—every commit, branch, and pull request automatically links to the right task. Developers in {city} push code and managers see progress instantly, no status meetings required. {vertical} teams ship faster when the code tells the whole story.

Team Management

Junior devs shouldn't access client billing. Contractors shouldn't see other projects. Set granular permissions that match how {vertical} actually work—by role, project, or even specific boards. Invite freelancers in {city} with time-limited access, track who did what, and revoke credentials in one click.

Frequently Asked Questions

Still have questions? Contact us at customer.service@gitscrum.com

What custom field types are available?

Text (single and multi-line), Number (integer and decimal), Dropdown (single select), Multi-select (multiple options), Date, Checkbox, User (assignee-type), and URL. Covers most tracking needs.

Can I make custom fields required?

Yes. Set any field as required. Task can't be created without filling it. Ensures data quality and consistency across your project.

Can different projects have different custom fields?

Yes. Each project can have its own set of custom fields. Bug tracker project has severity/environment. Feature planning has story points/risk. Customize per project.

Can I filter and sort by custom fields?

Yes. Full filtering support. Show only Critical bugs. Sort by story points descending. Group tasks by any custom field. Works in views and reports.

Ready to solve this?

Start free, no credit card required. Cancel anytime.