> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/platform/custom-fields/required-and-conditional-fields.md).
# Required and Conditional Fields
Different field types allow you to collect only the information relevant to the current Issue you're editing.
## Required Fields
Required fields must be filled in to save any change to an issue, from closing tickets to setting fields or assigning an issue. This is useful for making sure every issue is labeled for accurate analytics downstream as you grow your team. The set required fields will be applied on the[ issues page.](https://app.usepylon.com/issues/views/all-issues)
## Visibility Conditions
Conditionally show (and require!) fields based on the values in another field. For [issues](https://app.usepylon.com/settings/issue-sidebar?tab=configuration), this is useful for showing extra fields to gather information in different conditions (i.e. different details are needed for bugs vs. feature requests). Visibility conditions can also be used to conditionally show nested fields, such as a Sub-Product Area that shows only when a Product Area is provided.
For [accounts](https://app.usepylon.com/settings/account-sidebar?tab=configuration), use visibility conditions to selectively show fields based on the tier of customer or which products they have bought.
## Field value visibility
For issue **Select** and **Multi-select** fields, **Field value visibility** controls which options are available, while visibility conditions above control whether the whole field appears.
Open the field's **Settings** tab, add a condition under **When**, and use **Add Field Values** under **Display** to choose the options available when that condition matches. Each condition needs at least one field condition and one displayed value. Use **Add Condition** for additional cases.
* If several conditions match, the available options are the combined values from all matching conditions.
* If no condition matches, all options are available.
* Removing all conditions restores the full option list.
For example, show one set of Sub-product options when Product is A, and a different set when Product is B.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.usepylon.com/pylon-docs/platform/custom-fields/required-and-conditional-fields.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
