Rohan Swami Atlassian Team

Thanks @Erin Quick-Laughlin we don't have a timeframe for TMP support in Advanced Roadmaps but you can follow the progress here for updates: https://jira.atlassian.com/browse/JSWCLOUD-20012 @Maruf Mamurov we expect to support JWM at the same time as well.

@Su Wainwright as we release the feature we'll provide detailed instructions on how you can set up that issue hierarchy, but I can confirm now that it will be supported.

@Debra Jones Yes we'll use Status Category in the Done filter for consistency. Great to hear, @Trevor White !

@Coco S Chaussée as we roll out these changes, the filters and automation rules will automatically be migrated, there won't be any changes required from you. The Epic panel will show the new name when we roll out these changes. Please note that we don't have a release date yet, we'll share once we do.

@František Špaček _MoroSystems_ Short answer is we thought that approach would create too much complexity for users. Many customers use custom workflows and these don't set a resolution by default, so it's safer to use categories as all issue statuses belong to a category.

Hi @Gerardo Di Giuseppe , @Ste Wright is right this isn't supported natively today. However we're working on a solution for this, you can find the details here https://community.atlassian.com/t5/Jira-articles/Rename-epics-in-your-company-managed-projects/ba-p/1874726

@Curt Holley @Kresten @Paula Hidalgo @Mary Boyd Hi folks, answers to the most recent questions are below: Speaking of which, that is the only thing you need to prep for; any Saved filters or automation rules that reference type = Epic or the like. But my tip is, you can prepare (prior to changing the name) by editing them…

@Erin Quick-Laughlin in future you'll map to parent instead of epic link. Parent will be the super set of epic link and parent link. This means that there will be a single way to describe all parent-child relationships, and there won't be any confusion if customers were to rename Epic to another name of their choice.

@Curt Holley yes that's right, any changes now are safe. The feature will be released by the end of Q3 this calendar year, we'll have more precise dates as we get closer to release.

@Pablo Silva the JSW Cloud approach to issue hierarchy allows you to create issue types and levels for all your projects, then each project can adopt a subset of these issue types. For example, the level above Epic can contain Campaigns and Initiatives, Agile team projects can use Initiatives and Marketing teams can use…

hi @Sean F_ we will be introducing a new feature soon that may address your use case: https://community.atlassian.com/t5/Jira-articles/Rename-epics-in-your-company-managed-projects/ba-p/1874726

@alice lowah your needs might be addressed with this upcoming feature https://community.atlassian.com/t5/Jira-articles/Rename-epics-in-your-company-managed-projects/ba-p/1874726

@Paula Hidalgo The Epic Name field will still exist. The change that we are making is that the lozenges in the board/backlog will use the Issue Summary instead of the Epic Name. In the example below the Epic Name is Accounts, if the Issue Summary was The Accounts Team, the blue lozenges would update to The Accounts Team…

@Maite Rodriguez portfolioChildIssuesOf will be unaffected by the changes.

@Nigel Budd (CV) Thanks for the feedback on our edition-gating. The AR hierarchy and Issue hierarchy will indeed be combined as part of this work. @Kelly McConnell we'll be sharing details on our plans for the Epic name/summary fields well ahead of the release. For now, I can say that we'll reduce the usage of the Epic…

@Christina Robinson We've chosen this approach because it allows us to support multiple issue types at the Epic level in the future. Hierarchy config settings apply to the collection of issue types at that level, and Issue Types config applies to the Epic issue type specifically. The parent JQL function will replace the…

@Maite Rodriguez I've corrected that: Sub-tasks can only have a parent in their current project.

@Maite The subtask issue type can not be moved to another level and will not after these changes are rolled out. Sub-tasks can be moved to another project but the parent must be in the same project. @Sebastian Mühleis The hierarchy levels can be found by navigating to Plans (in the top nav) > Settings > Advanced Roadmaps…

@Maite Rodriguez Automation for epic links, parent links and epics will continue to work between Feb and May. It is only invalid epic link data that is affected from Feb 1, more details are here https://support.atlassian.com/jira-software-cloud/docs/maintain-epic-link-data-for-issues-above-the-epic-level/ In response to…

Hi @Nikki Zavadska _Appfire_ these levels above Epic can be created now in Premium.

Hi @Sabrina Beach I do indeed have an update - We’ve completed scoping and started working on this. We will be supporting: * Team-Managed projects in Advanced Roadmaps * Team-Managed projects used alongside Company-Managed projects in the same Advanced Roadmap This is a large piece of work touching many different parts of…

Yep that's the plan - Epics can be renamed to Features, and users can create an a new issue type called Epic to parent them. We intend to combine some of the functionality around epic-link and parent-link without losing any capabilities.

@Deepika.Kanaparthi @Curt Holley I'm happy to say that we are actively building a solution to this problem, shipping in 2022 Q2-Q3 calendar year. Premium customers will be able to implement a hierarchy of: 1. Epic 2. Feature 3. Story We've put this in the public roadmap here as Flexible naming of Epics.…

Hi David, The other comment here is correct, there are 2 types of projects: company-managed and team-managed. Currently Advanced Roadmaps support company-managed projects only, we are under way in our work to support team-managed as well. Please following this ticket for…

@josh_brozen @jennifer_hamilton I've emailed you, thanks.

Thanks @Fabian Lim and Kyle_Silverstein@discovery.com I've emailed you.

Hi Darrel, We're in the process of making improvements to the way parent link works. We are aiming for a consistent way of showing the relationship between an issue and its parent irrespective of where it sits in the hierarchy, thereby eliminating some of the inconsistent features across epic-link and parent-link including…

Hi Ofir, Please follow this ticket for the most updated information: https://jira.atlassian.com/browse/JSWCLOUD-20012 We're currently scoping out the work to support Team Managed Projects in Advanced Roadmaps. While I can't provide timelines right now, when we do have them they will be updated in the ticket above. Kind…

Were there challenges to teams adopting the issue hierarchy you put in place?

What kind of reports have you found most valuable in your team? especially for exec-level stakeholders.