# Feature Flag Detail Screen

This document introduces what you can see on the Feature Flag detail screen.

## Accessing the Detail Screen

You can access the detail screen of a specific Feature Flag after creating a new Feature Flag, or by clicking on a specific Feature Flag in the Feature Flag list.

## Detail Screen Layout

The Feature Flag detail screen shows the following content:

Feature Flags can only be used when the SDK version is at least 2.0.0. If you are using a lower SDK version, you must update. In that case, a warning banner will be displayed on the screen.

![Default content visible after creating a Feature Flag](/files/XdUXTGm8SYBXg0BWRmca)

1. **Feature Key**\
   When using Feature Flag-related methods in the SDK, the Feature Key is required as a parameter. The number displayed next to the Feature Key text is the Feature Key value — in this screenshot, it is 1.\
   Please share this key value and the [SDK](/en/development-guide/sdk.md) guide document with the developer in charge.
2. **Feature Flag Information**\
   The Feature Flag name and description entered during creation are displayed.
3. **Feature Flag Status**\
   You can set the Feature Flag status to on or off.
4. **Tab Menu**\
   Menus for the Feature Flag are provided as tabs. By default, the Traffic Settings tab is selected as shown in the image below.\
   (Traffic Settings, Parameter Settings, Real-time Exposure Status, Jira Integration, Change History)
5. **Schedule Settings**\
   Through Feature Flag Scheduling, you can set your desired release schedule in advance or schedule traffic changes for configured items.\
   For example, this is useful when you want to release a specific feature on time for a promotion launch and gradually increase traffic.\
   For more details, refer to the [Feature Flag Scheduling](/en/feature-flag/create-and-configure/feature-flag-scheduling.md) document.

### Traffic Settings

You can configure Feature Flag states such as User Targeting and Individual Targeting.

![Traffic Settings](/files/XrBmqPHzfu7haLJdMC4g)

1. **User Targeting**\
   Through User Targeting, you can gradually apply Feature Flag state values to users you want to target among all users.\
   You can configure what percentage of all users will encounter the feature corresponding to the Feature Flag True state. Additionally, you can add User Targeting to configure Feature Flag state values separately for users with specific properties.\
   The traffic ratio can be freely adjusted between 0 and 100, and you can also increase and then decrease it. For example, it is possible to set it to 80 and then adjust to 50, or to set it to 25 and then adjust to 50.\
   After setting the traffic ratio, click the **`Save`** button in the upper right corner to apply the changes.\
   For more details, refer to the [User Targeting](/en/feature-flag/create-and-configure/ff-targeting.md) document.

![Initial User Targeting screen](/files/9BjcemoFK9VxwJ2IZbdt)

![Example of gradual rollout to all users](/files/fZ9CNc18sFtXe3HgUvGd)

2. **Individual Targeting**\
   A feature that force-assigns specific users to always have the Feature Flag in an off or on state.\
   Configured using User Identifiers. Useful when you only want specific internal people to test.\
   Individual Targeting takes precedence over User Targeting. Click the **`Configure`** button on the right to set it in the dialog.

![Individual Targeting](/files/IYp5ViXAWyfzIAkMYpm6)

### Parameter Settings

You can use Parameter Settings to gradually apply flexible results to users.\
By setting parameter values for True and False, you can manage configuration values flexibly without separate code deployment.

For more details, refer to the [Parameter Settings](/en/feature-flag/create-and-configure/parameter-settings.md) document.

![Parameter Settings](/files/s34DfDKRsfajezClA6J4)

### Real-time Exposure Status Tab

You can see the number of users who encountered the Feature Flag on or off state within the last 30 minutes, along with information about those users (time, User Identifier value, status). The **`Update`** button becomes active every 30 seconds, so you can click it to refresh for the latest state.

![Real-time Exposure Status example](/files/c7JQpoRuuWsmdhYfMZ8t)

### Jira Integration Tab

You can manage Jira tickets linked to the Feature Flag within the Dashboard by integrating with Jira.

For more details, refer to the [Jira Integration](/en/external-link/jira-integration.md) document.

![Feature Flag with Jira ticket integrated](/files/SujkzaAzyieom4juyRSt)

### Change History Tab

Changes to the Feature Flag are recorded in chronological order.\
You can check the history of items created and edited by other collaborators through the Change History.

![Change History](/files/WbuCi3KFP4iu7jKdzH71)

Click "View Details" to see the details of the content before and after the modification.

![Change History — View Details](/files/23XvIRwwNTv9aEutKGLM)

## Feature Flag Additional Features

Click the **`・・・`** button in the upper right corner of the detail screen to see the additional features available for the Feature Flag.

![Feature Flag Additional Features](/files/XxwHfgVBqpKZOmnYEZJV)

### Edit Feature Flag Name

You can edit the Feature Flag name freely. Don't forget to click the **`Save`** button in the lower right corner after editing for changes to take effect.

![Edit Feature Flag Name and Description](/files/f6zQSMejGFgodNyiC3O9)

### Duplicate Feature Flag

Creates a copy of the Feature Flag.\
The result of copying can be seen in the Feature Flag list, with "(Copy)" appended to the name. For example, if you copy a Feature Flag named "Search Algorithm Improvement," the copy will be named "Search Algorithm Improvement (Copy)."

### Archive Feature Flag

You can archive the Feature Flag if it is no longer needed.\
Since an archived Feature Flag cannot be used again, please decide carefully.

![Archive Feature Flag](/files/Vdu2IkduZUz46r6lpBOI)

{% hint style="danger" %}
Before archiving, make sure to remove code related to the Feature Flag!

If left in place, you may encounter unintended errors.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.hackle.io/en/feature-flag/create-and-configure/ff-detail.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.