Irene Atlassian Team

@[deleted] , if you are referring to Parent field in particular, no not as yet. 

Hey @Brendan , No, not with Parent field either. It’s not (yet) possible to make the field mandatory as it’s not possible for every issue to have a parent, for example an issues on the top hierarchy level. If we are to make it mandatory, on our side we will need to add an exception for the top hierarchy level or any other…

@jacob.nielsen yes! The new Parent field will be fully rolled out by the end of this calendar year. It is already being rolled out for the Beta group customers (the expression of interest for that is already closed unfortunately in case you are interested) to get early feedback. Here for more…

Thank you @Ollie Peacey ! @Jose Rodriguez - swimlanes won't change as yet, it will work with only Epics level.

Hi @Mike Vitale , in that example you give, yes in Initiative issue view, you'll be able to add a child issue, which will be an Epic.

@Robin Powell just for Jira Cloud.

@Marion Richardson , that is unrelated to this change. The new 'Parent' field we describe in this post refers to a field inside Jira issue screens that is used to add a parent to the issue you are viewing. It's unrelated to the Epic issue type and unfortunately I also wouldn't know without looking at your instance further…

@fea yes there is. Invalid parent-child relationship won't be allowed.

@David Holman that's right! So cheer us as we are getting this to the finishing line 🙌 

@[deleted] , @Marion Richardson the new Parent field will be in Jira Work Management and Jira Service Management too. Re: the "Issues in this epic" on the screenshot you sent, @Marion Richardson , yes you're right - that's the current situation, but will soon be updated (you'll see the change in Beta).

@Tim Nelson the Parent field is a new field that will be rolled out to all plans.

@Gabriel Roth yes this is part of that big piece of work. However just want to note though that you can already do this now - you can create the structure you want: Add new hierarchy levels, include multiple issue types, and rename the hierarchy levels. This particular work on Parent field simplifies the parenting…

@Binoj Ammeripadath not sure if I understand 100% how you have set this up, but there doesn't seem to be anything we have changed that will block you from applying the same rules with Parent field.

@Ollie Peacey - we are opening up Beta to a bigger group of customers in Mid-October, and then aim to start the rollout from early November. Would love to hear a testimonial from you on how this feature will solve some problems from you! If you don't mind posting it here, or otherwise email me on: ireneo@atlassian.com .…

Hey all - just an update that this change will start rolling out from this week. It should take around 1 week to complete. Thanks! 

@Brittany Tryon , but I still want the epics to remain on the backlog panel AND keep all the child issues as Done? You can still do this, so all the child issues are Done, what you need to do is to keep the Epic issue status category as To Do / In Progress. This way the Epic will still remain on the backlog.

@Semir Beganovic this change we are doing with Epic Status doesn't touch/impact that "Export Excel" option. That one looks to be a Marketplace app (probably "Better Excel Exporter"), so probably someone in your instance had uninstalled the app. 

Hi @Alyssa Vassil we will start rolling out this change mid-end next week.

@Ryan Taylor , migrations won't be affected. The Parent field will read from the same place as the Epic Link & Parent Link field. So you will still see the same data, they will just be displayed as Parent field in Cloud. 

@Colton_Kosicek this will start rolling out from mid-end October. The public roadmap is here https://www.atlassian.com/wac/roadmap/cloud/flexible-naming-of-epics?p=c0c344ce-98 

@Peter Fjelsten , Parent = Epic-Key will just return that parent's child issues, not its grandchildren, as per current. Is that what you meant?

@Rick Olson , @Dean Leaso - apology for the late reply. Regarding automation: Existing automation will work as normal. There is no impact to them. However going forward, we recommend using the new Parent field where possible and will be displaying in-product notes to suggest users to not use the old fields. 

@Jaime Curtis ah you are on Team Managed Project. My tips above are for Company Managed Project =) For TMP, an Epic will be shown on the Panel as long as: 1. Epic issue status != Done 2. There are still Epic child issues that are not marked as Done So can you probably check (2) Epic child issues, see if there are still any…

@Jaime Curtis , if you want to hide that Epic again, expand the Epic on the Epic Panel and click on "Mark as Done". This will mark the Epic Status field as Done and hide the Epic away. The Epic Status field is not shown by default. To have it shown on the issue screen, you can go to the three dots icon on Epic issue view >…

@Jaime Curtis , Not rolled out yet. If they are already rolled out, this Epic should have stayed hidden as I can see from the screenshot, the Epic issue status is Done. You might want to check a field called "Epic status" to see if that has been amended recently.

@Brian Osam-Duodu Make sure that when you go into the Epic issue view, the issue status is also mark as Done, or belongs in a Done status category.

@Mpho Christina Roomane , no, this change only impact Jira Cloud. 

Hi @Rosana Casilli , if that Epic already has the correct status category (i.e the Epic is indeed already completed), then you don't need to do anything else. These epics will no longer be shown on your Epic Panel in near future.

Hi @Ravi Sagar _Sparxsys_ , Besides the community posts, there will be a number of in-product messaging that we will show to users & admins when they are performing actions that related to this. This shall also be included in the Jira Software newsletter that is sent to admins. 

@Alex Hoogendoorn Can you please take a look again now, the Epic progress insights should be using the Summary name now. Thanks.