---
title: "BigPicture: Clearing out the Task's status"
canonical: "https://support.appfire.com/space/SUPPORT/3045032137/BigPicture%3A%20Clearing%20out%20the%20Task's%20status"
format: markdown
---
# Clearing the Status Field in BigPicture

## Overview

BigPicture supports clearing the **Status** field, but the behavior depends on the type of task being updated.

## Jira Issues (Work Items) 

For Jira issues (work items), the **Status** field cannot be cleared.

This limitation exists because the Status field is a mandatory Jira system field that is managed through Jira workflows. Every Jira issue must always have a valid status assigned, and Jira does not allow issues to exist without one. As a result, BigPicture cannot remove or leave the Status field empty for Jira-based tasks.

## BigPicture-Only Tasks

For tasks that exist exclusively within BigPicture, the **Status** field can be cleared and left empty.

Examples of BigPicture-only tasks include:

- Components
- Sprints
- Versions
- Projects
- Other basic tasks created directly within a Box

Since these entities are not Jira issues, their status information is stored and managed solely within BigPicture. Unlike Jira, BigPicture does not enforce a mandatory status value for these task types.

## Summary

| Task Type | Can Status Be Cleared? | Reason |
| --- | --- | --- |
| Jira Issues (Work Items) | No | Jira requires every issue to have a valid status and manages status through workflows. |
| BigPicture-Only Tasks (Components, Sprints, Versions, Projects, etc.) | Yes | Status is stored only in BigPicture and is not subject to Jira workflow requirements. |

## Why the Difference Exists

The difference stems from Jira's data model and workflow requirements. Jira mandates that every issue has a status at all times, making it impossible to clear the field. BigPicture-only tasks are not governed by Jira workflows, which allows their Status field to remain empty when needed.