> ## Documentation Index
> Fetch the complete documentation index at: https://docs.custral.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Development

> The commits and pull requests that name a record, listed on the record and in a table column.

## Overview

A Development property lists the GitHub commits and pull requests that name a
record. Add it to an object once, and every record shows the work that
mentions its [ID](https://docs.custral.com/data/properties/text/id.md), newest first, as a property and
as a table column. Pick it from **Complex** in the property type list.

It is computed and read-only, like [Usage](https://docs.custral.com/data/properties/complex/usage.md):
nobody types into it, and the list is written by GitHub's deliveries. It has
no settings of its own.

## Configuration

![Creating a Development property.](https://docs.custral.com/images/screens/data/property-development-light.png)

Creating a Development property.

Development has no type settings, only the settings every property has
(name, description, **Required**, **Hidden by default**).

For anything to appear, the object needs:

* an [ID property](https://docs.custral.com/data/properties/text/id.md) with a prefix of at least two
  characters, such as `ISSUE-`, and
* the [GitHub integration](https://docs.custral.com/integrations/github.md) connected, so branch names,
  pull request titles and descriptions that mention `ISSUE-42` are matched to
  the record.

## What it shows

* **On the record**: one row per linked commit or pull request, newest first,
  with its state, its title linking out to GitHub, and its reference. Hover
  the row's branch icon to see what matched and where.
* **In a table**: the newest item's state and short reference (a commit's
  `abc1234` or a pull request's `#42`), plus a count of the rest, such as
  `#42 +1`. Open the record for the full list.

An object that has a Development property no longer shows the record page's
separate **Development** section, so the same links don't appear twice.

## What it stores

Nothing. The links are read when the record is read, from what GitHub has sent.
The property isn't included in spreadsheet exports.

## Filtering

None. A Development property can't be filtered or sorted.

## Examples

A Tickets object with a `TICKET-` ID property and a **Pull requests**
Development property: every branch called `ticket-128-fix-login` shows on
ticket `TICKET-00128`.

## Troubleshooting

| Symptom | Cause | What to do |
| - | - | - |
| The property is empty on every record | The object has no ID property, or its prefix is under two characters | Add an ID property with a prefix such as `ISSUE-` |
| A pull request naming the record doesn't appear | Two objects share that ID prefix and both hold a matching record, so neither is linked | Give the two objects different prefixes ([GitHub](https://docs.custral.com/integrations/github.md)) |
| Older pull requests are missing | Links fill in as GitHub sends updates, starting when the repository was connected | Expected; new and updated pull requests appear as they arrive |
| The property isn't in the add-filter list or the sort menu | Development can't be filtered or sorted | Filter on the record's other properties |

## See also

* [ID](https://docs.custral.com/data/properties/text/id.md): the identifier a commit or pull request names.
* [GitHub](https://docs.custral.com/integrations/github.md): how pull requests are matched to records.
* [Complex properties](https://docs.custral.com/data/properties/complex/overview.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.