Users are not able to add flag to the issue

Summary

Users may encounter the error "Flags cannot be added to issues (due to the configuration of the custom field "Flagged", which has no options available)" while trying to flag a work item.

Environment

Jira Cloud

Cause

Custom field "Flagged" might have improper context being set to it. Ideally, this field is locked, however, if you have migrated from Server, chances are that this field is not locked and you might have improper context for this field.

Solution

Check whether Flagged is editable The steps below only apply when the Flagged field isn't locked. You can't change the contexts, options, or default value of a locked field. If Flagged is locked, or you need help with its configuration, contact Atlassian Support.

Navigate to the custom field context of the field "Flagged"

• Select Settings (⚙) > Work items.

• In the Fields section of the sidebar, select Fields.

• Search for Flagged.

• If the field isn't locked, select More actions (…) > Contexts and default value.

Verify that the context is set to [CONTEXT LABEL] (all work types) and the option "Impediment" is enabled. If not, set the context to apply to all work types and enable the "Impediment" option.

Verify the flag

• Go to your board or backlog.

• Select the affected work item, then select More actions (•••) > Add flag.

If the flag is added, the problem is resolved. If you still see the error "Flags cannot be added to issues (due to the configuration of the custom field "Flagged", which has no options available)", reach out Atlassian Support if you need further assistance.