community.atlassian.com Open in urlscan Pro
2600:9000:2251:dc00:12:54e9:5100:93a1  Public Scan

Form analysis
1 forms found in the DOM

Name: form_1708a948803afa — POST https://community.atlassian.com/t5/blogs/v2/blogarticlepage.searchformv3.form.form

<form enctype="multipart/form-data" class="lia-form lia-form-inline SearchForm" action="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.searchformv3.form.form" method="post" id="form_1708a948803afa" name="form_1708a948803afa">
  <div class="t-invisible"><input value="blog-id/jira-software-articles/article-id/1307/q-p/dXRtX3NvdXJjZTphbGVydC1lbWFpbDo6dXRtX21lZGl1bTplbWFpbDo6dXRtX2NhbXBhaWduOmpzdy1lcGljLXN0YXR1c19FTUwtMTU5NjU6OmpvYmlkOjEwNjEyODE0Mzo6c3ViaWQ6MTcwNTExMjIyOA.."
      name="t:ac" type="hidden"><input value="search/contributions/page" name="t:cp" type="hidden"><input
      value="FYfiopgYaH4y-BDd2lYNOvUCfG30s_Lzzdc3TfYHplCpeZZqlW1SoNEG_n720oLV0nGBqSfUgdQ0BMgTchLRJ5mnE1KkB0J8BZHX1A87efc_dtormcOksN9t91CS9_vsTNZBZ0nrRu7BrUrWjPHUB9Sueq4bRFDPrrvp-S48rTfqHMx9AJzYZ96wwb1J9Yel_j0LLkDtl14W-sbYyv_CXqvc7Mk_dQr31R8vYvfNX5heKZsu-8mYWajfbI3udfpL5dYueVv7oFUOtvfp9qcyTEjyqm3Lt9K0uAqyR_8h3tSzkI5NbrSGf3dWLBI7c5bVp8cQb4kBZo9gsghdqHKMtNK9DwoCG-MsfHBbFAgDYsIe5GQwayqt6lQWQqMKPeNCbjITLllq3UM2wqZyEu4ohDN6z0C33tajMCCrk_LiYkcObL0SoK5HlOaHOaIfJDP15BAxYhSU8_dEop7A3b27P1XBNge3dycAS5yZ1vLCrllQ65Kka7r0LIMXHEIKM-twVOiw6HOpDKYecbYWkvRCKFrrJIlAyI_adYIOdcRxhfjKEH2d15CEVEl09dD1o9L3QB7cOdaayc95OLrkPFyVq_AW2y8iK_u_MJlUb-q1bS4Hc_bOpS0hXjqCqEeqVxv5AseAASTlubJJrwCtNiNaMNJA_8tKKbnbYucj63iBBodBMNrDmSgdgB1Alymfv1Nw50zGEgBkqCxBfpHsjdrjbULLU_0OnvTMAS5FRvcNR8n4LKlcllyrDflT9n00ThDXvxyA07t2AqGMWeW8aWtEm-rX3nKbuN_dFqm_p-_XmSxI-L1ttOxA1I31Aa_A8Nx5HsUtO6gZYy3drnHJeo_6vUVqCH4UB8eaM7QVbqg3lRrXNi7CQhPVNvGWFaw2r0CqIWQGpeA5p_7TDLqCWrE4qHOOPYvI45QBdiBGMT1JJYHqf230T94wdcFlbbbH94pVYW4az3b7LBJYKESb8MnFGIivKRQqaz4919ZZ4L7lYwAMMo_hXOfDFb2HIrG780eUjFEZCBm7D76A3XNdhLxTSpvYZjJeunAUDj6ZorZWMSKAYOi9FcxIySCn7JEHcKmdafQxjqlSe1bvHKMZvDka8iPkybsWKRrBgGY2Xr9xgbWOSgFCBx-y3cWNwRmeK-vcVfblrKO9Dom3x0XwCinRbqkEkk9-4gAGP2LBSRs6CM1NvX1cF-wDoq6IHfTGWZ5h-5IJgxq_-jfCJkllB-pqkoWW9Yj83tCvtdBQraPTduckV-vn_D6apWFyjpGn-RhnQxSpR0f1Wjnn87DDNG4y5YkcuDI_0wnj22KrNK63lDc."
      name="lia-form-context" type="hidden"><input value="BlogArticlePage:blog-id/jira-software-articles/article-id/1307:searchformv3.form:" name="liaFormContentKey" type="hidden"><input
      value="sBa7BmeE4XduoLxatHu8FzK0qJA=:H4sIAAAAAAAAALWSwUrDQBCGx0JPRQTRN9DrRtBeLB6KUDyEWgmeZbPZptEkG3cnTbz4KD6B+BI9ePMdfACvnjyYTWKJrWBS62mZf5b//2aYxzdoJyfQU5xKNjGYCFF6doyeCJUxoi4/LjpjIYPpIVGxHXhYPvozT1FJ6ArpEhpRNuEEacQVyrsuYUJy37OJTRUnfTsTKcOBx31nz+IYR/uXs87r7vNHCzZM6OTRwh/SgCNsm9d0Sg2fhq5hZUSh20sjhM0i+LQI/jt3vyn3SArGlbK0j1JZ2OzJORq/P7y0ANIoGYJZEyjIXDKx1LT3D5K6hXuAbBtly8pbOcm6o3RSO7mA85qmeGM3GmFneYSrg3/IK+Y4g0FN31hxWXVcqL/wt7ReXf/aEpoChwK/rWChngNrfTXgXxIK4PrnF0nhxAyrjsvS/NLL1mqXXisq5/8Ea/Bw3/cEAAA="
      name="t:formdata" type="hidden"></div>
  <div class="lia-inline-ajax-feedback">
    <div class="AjaxFeedback" id="feedback_1708a948803afa"></div>
  </div> <input value="GErv1OTN2mjbHomNTBW2mrVo-eNL_WzbQzSiDgwnfPA." name="lia-action-token" type="hidden"> <input value="form_1708a948803afa" id="form_UIDform_1708a948803afa" name="form_UID" type="hidden"> <input value=""
    id="form_instance_keyform_1708a948803afa" name="form_instance_key" type="hidden"> <span class="lia-search-input-wrapper"> <span class="lia-search-input-field"> <span
        class="lia-button-wrapper lia-button-wrapper-secondary lia-button-wrapper-searchForm-action" title="Search***" aria-label="Search***"><input value="searchForm" name="submitContextX" type="hidden"><input
          class="lia-button lia-button-secondary lia-button-searchForm-action" value="" id="submitContext_1708a948803afa" name="submitContext" type="submit"></span> <input placeholder="Search" aria-label="Search" title="Search"
        class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-message" value="" id="messageSearchField_1708a948803afa_0" name="messageSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Awaiting your command</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="DGB2o0MhlTE23Oq5XQHYhmVYn8CKhQwDcHMps3-FJVU." rel="nofollow" id="disableAutoComplete_1708a948ac4193" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-software-articles/article-id/1307/q-p/dXRtX3NvdXJjZTphbGVydC1lbWFpbDo6dXRtX21lZGl1bTplbWFpbDo6dXRtX2NhbXBhaWduOmpzdy1lcGljLXN0YXR1c19FTUwtMTU5NjU6OmpvYmlkOjEwNjEyODE0Mzo6c3ViaWQ6MTcwNTExMjIyOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input placeholder="Search" aria-label="Search" title="Search" class="lia-form-type-text lia-autocomplete-input search-input lia-search-input-tkb-article lia-js-hidden" value="" id="messageSearchField_1708a948803afa_1"
        name="messageSearchField_0" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Awaiting your command</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="m1zZcLJ8tQ6L4-1jxwCn1BM7zcYICmq50OhEpbGWBRU." rel="nofollow" id="disableAutoComplete_1708a94934c0e3" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-software-articles/article-id/1307/q-p/dXRtX3NvdXJjZTphbGVydC1lbWFpbDo6dXRtX21lZGl1bTplbWFpbDo6dXRtX2NhbXBhaWduOmpzdy1lcGljLXN0YXR1c19FTUwtMTU5NjU6OmpvYmlkOjEwNjEyODE0Mzo6c3ViaWQ6MTcwNTExMjIyOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input placeholder="Search all content" ng-non-bindable="" title="Enter a user name or rank" class="lia-form-type-text UserSearchField lia-search-input-user search-input lia-js-hidden lia-autocomplete-input"
        aria-label="Enter a user name or rank" value="" id="userSearchField_1708a948803afa" name="userSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Enter a user name or rank</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="5SKYICc-t53kT9xXoMAFFbD3x-yM80oUFvNJUDSZ2BE." rel="nofollow" id="disableAutoComplete_1708a9496d3393" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-software-articles/article-id/1307/q-p/dXRtX3NvdXJjZTphbGVydC1lbWFpbDo6dXRtX21lZGl1bTplbWFpbDo6dXRtX2NhbXBhaWduOmpzdy1lcGljLXN0YXR1c19FTUwtMTU5NjU6OmpvYmlkOjEwNjEyODE0Mzo6c3ViaWQ6MTcwNTExMjIyOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input title="Awaiting your command" class="lia-form-type-text NoteSearchField lia-search-input-note search-input lia-js-hidden lia-autocomplete-input" aria-label="Awaiting your command" value="" id="noteSearchField_1708a948803afa_0"
        name="noteSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Awaiting your command</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="Svy71l1w0A9sJkvif2g_37gJ-u69C5A_hc1NMxQZC-s." rel="nofollow" id="disableAutoComplete_1708a949a1c3f5" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-software-articles/article-id/1307/q-p/dXRtX3NvdXJjZTphbGVydC1lbWFpbDo6dXRtX21lZGl1bTplbWFpbDo6dXRtX2NhbXBhaWduOmpzdy1lcGljLXN0YXR1c19FTUwtMTU5NjU6OmpvYmlkOjEwNjEyODE0Mzo6c3ViaWQ6MTcwNTExMjIyOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input title="Awaiting your command" class="lia-form-type-text ProductSearchField lia-search-input-product search-input lia-js-hidden lia-autocomplete-input" aria-label="Awaiting your command" value=""
        id="productSearchField_1708a948803afa" name="productSearchField" type="text" aria-autocomplete="both" autocomplete="off">
      <div class="lia-autocomplete-container" style="display: none; position: absolute;">
        <div class="lia-autocomplete-header">Awaiting your command</div>
        <div class="lia-autocomplete-content">
          <ul></ul>
        </div>
        <div class="lia-autocomplete-footer">
          <a class="lia-link-navigation lia-autocomplete-toggle-off lia-link-ticket-post-action lia-component-search-action-disable-auto-complete" data-lia-action-token="SVtTUgpJui_tvXgOVVUO37i5BghwnD2UIE9Kc5DTnJY." rel="nofollow" id="disableAutoComplete_1708a949d4afc8" href="https://community.atlassian.com/t5/blogs/v2/blogarticlepage.disableautocomplete:disableautocomplete?t:ac=blog-id/jira-software-articles/article-id/1307/q-p/dXRtX3NvdXJjZTphbGVydC1lbWFpbDo6dXRtX21lZGl1bTplbWFpbDo6dXRtX2NhbXBhaWduOmpzdy1lcGljLXN0YXR1c19FTUwtMTU5NjU6OmpvYmlkOjEwNjEyODE0Mzo6c3ViaWQ6MTcwNTExMjIyOA..&amp;t:cp=action/contributions/searchactions">Turn off suggestions</a>
        </div>
      </div> <input class="lia-as-search-action-id" name="as-search-action-id" type="hidden">
    </span> </span> <span id="clearSearchButton_1708a948803afa" role="button" tabindex="0" title="Clear" class="lia-clear-field lia-js-hidden" aria-label="Clear the search input"></span> <span class="lia-cancel-search">cancel</span>
</form>

Text Content

Atlassian Community logo Products Interests Groups
Create
Ask the community 

 * ASK A QUESTION
   
   Get answers to your question from experts in the community

Awaiting your command

Turn off suggestions
Awaiting your command

Turn off suggestions
Enter a user name or rank

Turn off suggestions
Awaiting your command

Turn off suggestions
Awaiting your command

Turn off suggestions
cancel
Turn on suggestions
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in Kudos

YOU’RE LOGGED OUT

Log in to ask questions, follow content, and engage with experts

Log in to the community


PRODUCTS

 * Jira
   Jira
 * Jira Service Desk
   Jira Service Management
 * 
   Jira Work Management
 * 
   Compass
 * jira-align
   Jira Align
 * Confluence
   Confluence
 * Trello
   Trello
 * 
   Atlas
 * Bitbucket
   Bitbucket

See all

COMMUNITY RESOURCES

 * Announcements
 * FAQ
 * Guidelines
 * About

SUPPORT

 * Technical support
 * Documentation
 * Atlassian Community Events
 * Atlassian University

INTERESTS

 * Feedback Forum
   Announcements

See all

COMMUNITY RESOURCES

 * Announcements
 * FAQ
 * Guidelines
 * About

SUPPORT

 * Technical support
 * Documentation
 * Atlassian Community Events
 * Atlassian University

TOP GROUPS

 * groups-icon
   Welcome Center
 * groups-icon
   Featured Groups
 * groups-icon
   Product Groups
 * groups-icon
   Regional Groups
 * groups-icon
   Industry Groups
 * groups-icon
   Community Groups

Explore all groups

COMMUNITY RESOURCES

 * Announcements
 * FAQ
 * Guidelines
 * About

SUPPORT

 * Technical support
 * Documentation
 * Atlassian Community Events
 * Atlassian University


EARN BADGES AND MAKE PROGRESS

You're on your way to the next level! Join the Kudos program to earn points and
save your progress.

Deleted user

Level 1: Seed



25 / 150 points

Next: Root

1 badge earned


PARTICIPATE IN FUN CHALLENGES

Challenges come and go, but your rewards stay with you. Do more to earn more!




GIFT KUDOS TO YOUR PEERS

What goes around comes around! Share the love by gifting kudos to your peers.




RISE UP IN THE RANKS

Keep earning points to reach the top of the leaderboard. It resets every quarter
so you always have a chance!



Join now to unlock these features and more

Join the Kudos program



COME FOR THE PRODUCTS,
STAY FOR THE COMMUNITY

The Atlassian Community can help you and your team get more value out of
Atlassian products and practices.

Get started Tell me more
4,588,688
Community Members
4,705
Community Events
190
Community Groups
 * Community
 * Products
 * Jira
 * Jira Software
 * Articles
 * Upcoming: The backlog epic panel will soon use epics' Issue status category


UPCOMING: THE BACKLOG EPIC PANEL WILL SOON USE EPICS' ISSUE STATUS CATEGORY

May 29, 2023

Hi Jira Community! 👋

We announced last year that we’re making changes to epic fields in
company-managed projects.

As part of these changes, we highlighted that epic status will no longer be used
and we will use an epic’s Issue status category instead to determine whether an
epic will be displayed on the backlog’s epic panel.

This change will happen in August 2023.

Continue reading to learn how these changes might impact you and what you can do
to prepare.


WHAT’S CHANGING?

Previously, the backlog’s epic panel used an epic’s Epic status value to
determine whether an epic would be displayed. By default, the Epic status is
only accessible from the epic panel, otherwise admins had to configure a field
for it to be visible in the issue view.

Additionally, epics that were marked as Done were hidden from the epic panel
list, regardless of the status of their child issues.

We’ve changed the logic of the epic panel slightly to respect the epic’s Issue
status category instead. If you've created custom statuses in the
Done category, the epic panel will behave as if the epic was complete if it is
using one of these statuses.

HOW THIS CHANGE IMPACTS YOU:

 * If you have epics whose Epic status is marked as Done but the epic’s Issue
   status category is not Done, these epics will re-appear on your backlog epic
   panel.

 * If you have epics whose Epic status is not Done but the epic’s Issue status
   category is Done, these epics may disappear from your backlog epic panel if
   all of its child issues are also marked as Done.



WHAT YOU CAN DO TO PREPARE:

We’ve provided a couple of JQL scripts for you to identify any Epics that have a
different Epic status to their Issue status category. You can then use Jira’s
bulk change functionality to update these statuses to match.

Our rollout begins in August 2023, so you’ll have until the end of July 2023 to
review your epics.

To view the epics that will appear in the epic panel once this change rolls out,
use the following JQL in Advanced Search:

"Epic Status" = "Done" and statusCategory in ("To Do","In Progress")

To view the epics which may disappear from the epic panel once this change rolls
out, use the following JQL in Advanced Search:

"Epic Status" != "Done" and statusCategory in ("Done")

 


WHAT'S NEXT

We'll begin progressively rolling out these updates from August 2023.

Keep an eye out here on the Atlassian Community for more information as we get
closer to release.

In the meantime, if you have any questions or feedback on these updates, let us
know in the comments below. Thanks all!

Comment
Watch
Like 31 people like this # people like this
Share
 * LinkedIn
 * Twitter
 * Email
 * Copy Link

21673 views



24 COMMENTS

Ann Rumenapp Jul 03, 2023

Question - How do I bulk change the statusCategory field to set it to done? 
There are 640+ epics in my instance with "Epic Status" = Done that need the
statusCategory also set to done.



Like • 9 people like this 9 people like this
Rodrigo Angulo Jul 06, 2023

The statusCategory is a grouping of the statuses. By default those green status
are considered done. If you you use type = epic AND statusCategory = Done you in
the advanced issue navigator you be able to bulk change and transition these
statuses. @Ann Rumenapp 



Like • 2 people like this 2 people like this
Lauren Jul 06, 2023

YES! Can't wait. This has been such an admin overhead.



Like • 8 people like this 8 people like this
Michael Payne Jul 06, 2023 • edited

I found a dozen or so Epics with Epic Status done but statusCategory not done,
with no ability that I could see to change the status category. Please explain
how to do this - or will it only be possible after the change is made in August?
The comment above did not resolve the issue in bulk change. Do the workflows
themselves have to be modified?



Like
Gary Spross
Rising Star

Rising Star
Rising Stars are recognized for providing high-quality answers to other users.
Rising Stars receive a certificate of achievement and are on the path to
becoming Community Leaders.
Get recognized
Jul 06, 2023

@Michael Payne & @Ann Rumenapp, you can do an advanced search of 

issuetype = Epic AND "Epic Status" = Done AND statusCategory != Done

For all of the issues that are returned, do a bulk update and set the status
(you can't set the "statusCategory") to whatever completed status the associated
workflow has ("Done" or "Closed" for example). 

@Rodrigo Angulo, was simply pointing out that if you take a look at the
associated workflow, any status in green is of the statusCategory "Done".



Like • 2 people like this 2 people like this
Amanda Ward Jul 06, 2023

Why are there two status fields???



Like • 7 people like this 7 people like this
Melissa Burns Jul 06, 2023

Greetings! I have a question regarding Epics. If an Epic has no assigned issues,
will it disappear or still be visible? I'm working on a complex project and want
to ensure that my future Epics are secure. Should I add some tasks to prevent
them from disappearing? Please feel free to ask any additional questions. Thank
you.



Like
Patrick van der Rijst Jul 06, 2023

@Amanda Ward that's what Atlassian is trying to solve here. "Epic Status" is
being deprecated and will respect the actual issue's status. 

You can already prepare for this by setting up automation rules that sets the
Epic Status to Done whenever an epic is transitioned to a Done status category
and vice versa. 



Like • 2 people like this 2 people like this
Gary Spross
Rising Star

Rising Star
Rising Stars are recognized for providing high-quality answers to other users.
Rising Stars receive a certificate of achievement and are on the path to
becoming Community Leaders.
Get recognized
Jul 06, 2023

@Melissa Burns, empty Epics will continue to show within the Epics panel as long
as the Epic's issue status is not in the "Done" category (i.e. a green colored
status).



Like
Dan W Jul 06, 2023

Will this be implemented even if we don't have the epic name-->Summary change
applied to our system yet?



Like
Ciaran Jul 06, 2023

It looks like Epics with the child issues marked as Cancelled will reappear
until they are marked as Done, which isn't ideal depending on your reporting
needs. 



Like
Gary Spross
Rising Star

Rising Star
Rising Stars are recognized for providing high-quality answers to other users.
Rising Stars receive a certificate of achievement and are on the path to
becoming Community Leaders.
Get recognized
Jul 06, 2023

@Ciaran, not if you set the issue status as Done. See instructions in above
comments.



Like • Ciaran likes this
Yatish Madhav Jul 06, 2023

Thank you for this ... Looking forward to this update. Although, in an instance
with almost a 1000 projects, I wonder what backlash this may have ... I do have
some issues showing based on both the JQLs that you have provided but I wonder
if and how they will impact project managers if and when they use the Epic panel
in the backlog. Thank you



Like
Ibrahim Apena
I'm New Here

I'm New Here
Those new to the Atlassian Community have posted less than three times. Give
them a warm welcome!
Get involved
Jul 07, 2023

In line with @Melissa Burns  comment and @Patrick van der Rijst  response, 

 * I do not use  statuscategory  but "Epic status" 
 * if the "Epic status" is deprecated as i understood , it mean all the epic in
   the backlog panel will disappear ?
 * To avoid the above 
   * i have to configure all epics to start using statuscategory  
   * then migrate all the "epic state" to statuscategory  

is my understanding correct. 



Like • NatasjaP likes this
BeeFC Jul 07, 2023

This is a welcoming change. A.K.A. change for the better!



Like
Gary Spross
Rising Star

Rising Star
Rising Stars are recognized for providing high-quality answers to other users.
Rising Stars receive a certificate of achievement and are on the path to
becoming Community Leaders.
Get recognized
Jul 07, 2023

@Ibrahim Apena, the "statusCatgegory" is a bucket that a status falls into.
There are 3 status categories: To Do, In Progress, & Done. These are set by
Atlassian. Every status falls into one of those three categories. Epics are
issue types, therefore they follow a workflow. A workflow is comprised of
statuses and, as indicated previously, the statuses fall into status
categories. 

You don't have to configure the Epics in any way other than to ensure that the
issue status they are set to is actually correct. If the issue status of an Epic
is in the To Do or In Progress status category, then the Epic will show within
the Epic backlog. If the issue status of an Epic is in the Done status category,
then the Epic will NOT show within the Epic backlog.

You can follow the instructions within my previous comments to perform a search
and bulk update the issue status of your Epics to ensure you won't have any
issues when the update is implemented.



Like • Ibrahim Apena likes this
Barbara Shaw Jul 07, 2023

@Patrick van der Rijst could you please share how you configured your automation
rule for this? ("that sets the Epic Status to Done whenever an epic is
transitioned to a Done status category and vice versa")



Like
Jesse Geiger Jul 10, 2023

Nothing sets a Status Category except when you first create the Status. You have
to pick one of the 3 categories. After that, that's it. Grey, Blue, or Green.

I'd like to bring up the difference between using a Status and a RESOLUTION for
Epics (or any other issue type). Don't forget about that resolution field. 
Instead of creating 6 different green stauts values for Done, Complete,
Cancelled, Denied, or whatever, just keep the 1 "Done" green status, and create
additional resolutions for the Done status.  The Epic is Done but Cancelled.
Done and Completed. If anything, reporting is easier because you can refine to a
second level (resolution). 

My workflows have automations that allow the users to choose their resolution
and automatically set values.



Like
Gary Spross
Rising Star

Rising Star
Rising Stars are recognized for providing high-quality answers to other users.
Rising Stars receive a certificate of achievement and are on the path to
becoming Community Leaders.
Get recognized
Jul 10, 2023

@Barbara Shaw, I use the following automation to ensure the Epic status aligns
with the Issue Status the Epic is transitioned to. I run this rule globally.

Note: You have to set the "Epic Status" within the Advanced section as it's not
a selectable field.

This rule becomes obsolete once the changes mentioned in this post are rolled
out (since the "Epic Status" field basically becomes unused).





Like • 3 people like this 3 people like this
Barbara Shaw Jul 10, 2023

@Gary Spross thank you so much very helpful ^^^



Like • Gary Spross likes this
Suresh_Mantrala Jul 11, 2023 • edited

In Jira Cloud, before removing the Epic Status field from Epic screens,
regarding the data-at-rest (existing Epics)

1. For the issues matching the query "Epic Status" = "Done" and statusCategory
in ("To Do"), we can bulk update Epic Status to To Do and similarly
for statusCategory in ("In Progress") to Epic Status = In Progress, so that
Epics appear in the Epics Panel.

2. Not sure, why does Atlassian say - To view the epics which may disappear from
the epic panel once this change rolls out using the query "Epic Status" != Done
AND statusCategory in (Done).  As such these do not appear in the Epics Panel as
they are of StatusCategory = Done. Even if Epic Status of these is bulk-updated
to Done (for data sanity), why would they disappear, when they are already
disappearing right now. Can someone explain?



Like
Michael Payne Jul 11, 2023

@Suresh_Mantrala : regarding #2, "Not sure, why does Atlassian say - To view the
epics which may disappear from the epic panel once this change rolls out using
the query "Epic Status" != Done AND statusCategory in (Done).": so right now,
the epic panel runs off of the Epic Status field NOT statusCategory. So an Epic
with status !=Done appears in the panel, regardless of statusCategory. After the
change, the epic panel will use statusCategory, NOT Epic Status. At that point,
if an Epic has a status of not Done, but a statusCategory of Done, it will drop
off the panel, because the panel criteria is only looking at statusCategory
(there are some complexities with Epic issues, but that is the gist of it).



Like • Barbara Shaw likes this
Reinado Alves Santos
I'm New Here

I'm New Here
Those new to the Atlassian Community have posted less than three times. Give
them a warm welcome!
Get involved
Jul 17, 2023

Gostei muito desta atualização citada sobre o épico. Parabéns!!!



Like
Rosana Casilli Jul 17, 2023

So If  the category status of an epic is Done, then I do not need to perform any
changes realted to this change righ?



Like


COMMENT

Log in or Sign up to comment


WAS THIS HELPFUL?

Yes No

THANKS!

×

Irene

Atlassian Team

Atlassian Team
Atlassian Team members are employees working across the company in a wide
variety of roles.

ABOUT THIS AUTHOR

Senior Product Manager

Atlassian

Sydney, Australia

6 accepted answers

55 total posts

 * 
 * 
 * 
 * 
 * 
 * 
 * +16 more...

View profile
Jira Software
Jira Software

TAGS

 * cloud
 * epic
 * jira-software-cloud

Related Community content


 * BACKLOG AND EPIC PANEL


 * RE: CANNOT SEE EPICS ON ADVANCED ROADMAP WHEN EPIC...


 * ISSUES (EPICS AND TASKS) IN TE STATUS BACKLOG DO N...


 * RE: HOW DO I RESTORE AN EPIC TO THE EPIC PANEL ONC...


 * KANBAN BACKLOG EPIC PANEL - HIDE COMPLETED EPICS?




HELP US PLANT 30,000 TREES IN JULY! ARE YOU A KUDOS MEMBER YET?

For every like, share, or RSVP during July, we will plant one real-life tree -
up to 10,000 trees each in Brazil, Ethiopia, and Haiti. Join us in Likes for
Trees 2023!

Start planting now
AUG Leaders


UPCOMING JIRA SOFTWARE EVENTS

JIRA PRODUCT DISCOVERY EXPLAINED →

Jul 18
Maidenhead, England (GB)

LETS LEARN ABOUT ATLASSIAN INSIGHTS! →

Jul 18
Columbus, OH (US)

REIMAGINING RELEASE NOTES: LEVERAGING JIRA TO CRAFT COMPELLING UPDATES →

Jul 19
Düsseldorf, NRW (DE)
See all events
 * FAQ
 * Community Guidelines
 * About
 * Privacy policy
 * Notice at Collection
 * Terms of use
 * © 2023 Atlassian




Auto-suggest helps you quickly narrow down your search results by suggesting
possible matches as you type.


This site uses cookies to improve your browsing experience, perform analytics
and research, and conduct advertising. To change your preferences, click Cookie
Settings. Otherwise, clicking Accept all Cookies indicates you agree to our use
of cookies on your device. Clicking Reject all means you do not agree to our use
of non-strictly necessary cookies on your device.Atlassian Cookies and Tracking
Notice
Manage preferences Reject all cookies Accept all cookies



MANAGE PREFERENCES

When you visit any website, it may store or retrieve information on your
browser, mostly in the form of cookies. This information might be about you,
your preferences or your device and is mostly used to make the site work as you
expect it to. The information does not usually directly identify you, but it can
give you a more personalized web experience. Because we respect your right to
privacy, you can choose not to allow some types of cookies. Click on the
different category headings to find out more and change our default settings.
However, blocking some types of cookies may impact your experience of the site
and the services we are able to offer.
More information
Accept all

STRICTLY NECESSARY COOKIES

Always Active

These cookies are necessary for the website to function and cannot be switched
off in our systems. They are usually only set in response to actions made by you
which amount to a request for services, such as setting your privacy
preferences, logging in or filling in forms. You can set your browser to block
or alert you about these cookies, but some parts of the site will not then work.
These cookies do not store any personally identifiable information.

TARGETING COOKIES

Targeting Cookies

These cookies may be set through our site by our advertising partners. They may
be used by those companies to build a profile of your interests and show you
relevant adverts on other sites. They are based on uniquely identifying your
browser and internet device. If you do not allow these cookies, you will
experience less targeted advertising.

FUNCTIONAL COOKIES

Functional Cookies

These cookies enable the website to provide enhanced functionality and
personalisation. They may be set by us or by third party providers whose
services we have added to our pages. If you do not allow these cookies then some
or all of these services may not function properly.

PERFORMANCE COOKIES

Performance Cookies

These cookies allow us to count visits and traffic sources so we can measure and
improve the performance of our site. They help us to know which pages are the
most and least popular and see how visitors move around the site. If you do not
allow these cookies we will not know when you have visited our site, and will
not be able to monitor its performance.

Back Button


COOKIE LIST



Search Icon
Filter Icon

Clear
checkbox label label
Apply Cancel
Consent Leg.Interest
checkbox label label
checkbox label label
checkbox label label

Reject all Confirm my choices