---
title: Case fields
url: https://www.tines.com/docs/cases/case-fields/
updated: 2026-05-06T17:18:42+00:00
---

*[tines.com](https://www.tines.com/llms.txt) › [Docs](https://www.tines.com/llms.txt) › [Cases](https://www.tines.com/llm/docs/cases.md)*

# Case fields

*[View on tines.com](https://www.tines.com/docs/cases/case-fields/)*

Case fields let you capture custom, structured data within your cases. Data like ticket IDs, affected systems, or investigation outcomes. These fields extend beyond the built-in case properties like name, status, and priority.

### How case fields fit into Cases

Case fields follow a define-once, use-everywhere pattern:

1. **Define** fields in your team's case settings – choose a type, set validation rules, and mark fields as sensitive if needed.
2. **Attach** fields to cases – add case fields and field groups within a case and case template, or automatically attach fields to cases via story actions.
3. **Interact** with field values – view and update case fields in the cases sidebar or wherever they are mentioned within a case, via story automation, or dynamically within a page.
4. **Report** on field data – filter the case list and board by field values, or report on case field data within dashboard charts.

### Key concepts

- **Field types** – every field has a type (text, number, timestamp, or boolean) chosen at creation. The type determines the input control and cannot be changed later.
- **Validation** – text fields optionally support validation: a fixed list of allowed values or a regex pattern. Other field types do not support validation.
- **Sensitive fields** – fields [marked as sensitive are redacted](https://www.tines.com/docs/sensitive-case-fields/) for users without the *View sensitive information* permission, including in the activity timeline and `@` mentions within the case body. 
- **Groups** – fields can be organized into named, collapsible groups (displayed as folders in the case sidebar) keeping related fields together. Groups are a convenient way to interact with a large number of related fields in cases, search, and dashboards.
- `**@**`** mentions** – reference a field's live value directly in case descriptions, notes, and comments by typing `@` and selecting the field name. Mentions allow you to update the field value inline, continuing through the case uninterrupted.

> **NOTE:** When working with case fields in a story or via API, fields may be referred to as "inputs".

### Define and configure fields

Fields are created and managed in your team's case settings. Fields defined within a team *cannot* be seen or used by other teams. From here you can:

- Add, rename, and delete fields
- Configure validation rules (fixed list or regex)
- Mark fields as sensitive — see [Sensitive case fields](https://www.tines.com/docs/sensitive-case-fields/)
- Organize fields into groups

![](https://www.datocms-assets.com/55802/1775256961-doc-case-fields-settings.png)

### Interact with fields within a story or via API

Once defined, fields can be further leveraged with using the **Create case** story tile, our story templates, or via the API.

- Create case story tile requires that you select a team to proactively load which fields can be added to the case.
- When using [story templates](https://www.tines.com/docs/templates/) or the API, they may refer to case fields as `case inputs`
- `Load case field IDs, names, and values quickly in a formula`

> **NOTE:** Reference \`INFO.cases.inputs\` to quickly reference a specific case field ID, name, or predefined values.



### Use fields within a case

Once defined, fields can be added to individual cases or case templates to capture case-specific data. You can also reference field values inline using `@` mentions.

- Add, edit, and remove field values
- Mention fields in descriptions, notes, and comments

![](https://www.datocms-assets.com/55802/1775256897-doc-case-fields-in-case-example.png)

[](https://demo.arcade.software/EFzjj6X99dmOQl0ON5ca?embed&embed_mobile=tab&embed_desktop=inline&show_copy_link=true)

### Automate and report on fields

- **Story actions** – set field values automatically when creating or updating cases from a story.
- **Search and filtering** – filter cases by field values, combine conditions with AND/OR logic, and save filtered views.
- **Dashboards** – use case fields as a data source in dashboard charts to visualize trends across cases. See [Dashboards](https://www.tines.com/docs/dashboards/)

![](https://www.datocms-assets.com/55802/1775259057-doc-case-fields-dashboard.png)

### Permissions

Access to case fields is controlled by your roles and permissions. 

Creating, updating, and deleting field definitions requires *Case field* permissions on custom roles, or the *Manage cases* permission.

Viewing sensitive field values requires the *View sensitive information* permission.

### Limits

<table border="1" style="border-collapse: collapse;"><colgroup><col style="width: 59.2466%;"><col style="width: 40.8598%;"></colgroup><tbody><tr><th>Resource</th><th>Limit</th></tr><tr><td>Fields defined per team</td><td>1,000</td></tr><tr><td>Fields added to a case</td><td>100</td></tr><tr><td>Fixed list options for a field</td><td>75</td></tr><tr><td>Text field type length</td><td>1,000 characters</td></tr></tbody></table>

### Related pages

- [Case limits](https://www.tines.com/docs/limits/)
- 
- [Components of a case](https://www.tines.com/docs/components/)