Difference between status and epic status for the EPIC

[Ramesh Krishnan]

Difference between status and epic status for the EPIC, 

[Evgenii · Accepted solution]

Hi, @Ramesh Krishnan 

Important Notice - in Jira Cloud this functionality is deprecated. It exists on  some server/data center versions.

But answering on your question - in Jira, both Status and Epic Status were used to track the progress of issues, but they serve different purposes within the context of epics.

Status

- Scope: Applies to individual issues.
- Values: Commonly includes stages like "To Do," "In Progress," "Done," etc. This depends on your workflow and can be customized.
- Usage: The status field shows where a single issue is in the development process. For example, an issue might start as "To Do," move to "In Progress," and finally be marked as "Done."
- Example: An issue like "Fix a bug" might have statuses like "To Do," "In Progress," and "Done."

Epic Status

- Scope: Applies specifically to epics.
- Values: Default values often include "To Do," "In Progress," and "Done." This can also be customized.
- Usage: The epic status field provides an overview of the progress of the entire epic, which can contain multiple issues. 

Key Differences

- Scope: Status is for individual issues, while Epic Status is for the epic as a whole.
- Values: Both can use similar values, but their interpretation differs. For example, "To Do" in status means one issue is still pending, whereas in Epic Status it might mean some of the issues in the epic are pending.

Relationship

An epic can have multiple issues with different statuses. However, its own Epic Status provides a high-level view of the progress of those issues collectively.

Conclusion

The main distinction between the two is that Status tracks the progress of individual issues within an epic, while Epic Status gives a broader picture of the epic's overall progress.

If you need more detailed information, you can look at this sorces:
https://confluence.atlassian.com/jirasoftwareserver0811/working-with-epic-statuses-1019393039.html
https://support.atlassian.com/jira/kb/linking-epic-status-to-the-epic-issue-status/
https://support.atlassian.com/automation/kb/updating-epic-status-based-on-epic-workflow-status-transition/
https://community.atlassian.com/forums/Jira-questions/Define-Epic-Status/qaq-p/2702377

[John Funk]

The Epic Status field has been deprecated in Jira Cloud. 

[Evgenii]

@John Funk yes, exactly. It's not working. My answer was about difference, how they differ. I'll add it to my answer.

[Trudy Claspill · Accepted solution]

Hello @Ramesh Krishnan 

The tags on your post indicate you are using Jira Cloud. If that is accurate then be advised that the Epic Status field has been deprecated and is no longer used, though it has not yet been removed.

As @Kristian Walker _Adaptavist_ it was previously used to determine if the Epic would display in the Epics Panel in agile board Backlog screens.

However, the same field was never part of the Team Managed project architecture.

In 2023 in an initiative to align Team Managed and Company Managed projects, the deprecation of that field (along with Epic Summary) was announced.

https://community.atlassian.com/forums/Jira-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562

[Kristian Walker _Adaptavist_ · Accepted solution]

Hi Ramesh,

The Epic Status field is a system field used b Atlassian to determine how the Epic is displayed in the Epics panel on board as mentioned here.  

The Status field is the regular status field mapped to the workflow used by the Epic Issue type. 

I hope this information helps.

Regards,

Kristian