Rohan Swami Atlassian Team

Hi @Sarah Green @Evolve Integration thanks for your patience. There are possibly 2 issues in play here: * The weighted score formula is based on all the ideas in your project, not based on the filters you've applied to the view. Customers have given us feedback that they expect it to be calculated based on visible ideas…

Thanks for the feedback @Ben Arundel. As @Erin Mihalik said your best option for doing this within Jira Product Discovery is to comment on the idea itself, but if you want to get a lot of comments on a subset of the text then Confluence is more appropriate.

@Bill Sheboy we don't expect impacts but rest assured that if there are, we will give you plenty of notice and detail ahead of the changes impacting you.

@Sarah Green @Karim ABO HASHISH @Kevin Ulland thanks for your feedback on how we can improve the depth of Salesforce integration for you. While we don't have near term plans for this, it's very helpful for us in working out what to build next. As I think you've already found, here's the post with our existing integrations.

Hi Ben, No risk at all! These are placeholder fields to give you an idea of what you can do, it's totally your choice in which fields you want to add or remove. If your goals are links I would suggest creating a new field of type 'Hyperlink'.

Hi @Sarah Green do you also have other ideas that are getting a different score?

@Ronke I've sent you a direct email. @Nouman Riaz I've shown the summary, description and name fields below

@Ronke We have a guide to identifying and fixing impacted epic-links here. Please create a support case or add another comment here if it doesn't give you the information you need.

Hi @Patricia Francezi_iDev_ , if you have added another issue type to the epic level then you can make it a parent to a story by using the parent-link field rather than the epic-link field. It's not currently in our roadmap to support more issue types at the epic level, please give this an upvote to express your interest…

@Mark Thompson I've sent you a direct email to follow up on this and I'll do my best to help you out.

@Chris Charensac only issues at the Story level can be connected to epics using epic-link. Based on the hierarchy you have shared the following JQL should identify issues at risk: issuetype in (Initiative, Key Result) and "Epic Link" is not EMPTY All the best!

@Mark Thompson The only change shipping on October 31st is the removal of invalid epic links (full details here https://support.atlassian.com/jira-software-cloud/docs/maintain-epic-link-data-for-issues-above-the-epic-level/#Invalid-epic-link-relationships-will-be-deleted-), we've given customers several months to prepare…

Hi all! We now have a beta version of this feature available for you to test out. There are a few limitations in the beta that are important to know before you enable it: * No support for levels above Epic. ie. You can only have a hierarchy of Subtask-Story-Epic(renamed). * No support for Automations, custom workflows or…

@Su Wainwright if you set up EPIC-FEATURE-STORY you will not be able to link Stories directly to Epics, as parents must be from one level above. Currently we do not support skip-level parenting and it is not in our plans to do so. We've seen a lot of customers use 'placeholder' Features in this scenario that might be the…

Hi folks, Jira Product Manager here. We'll be supporting selecting an epic/parent when creating an issue for next-gen projects in the coming months. I appreciate this is a long time coming. While I can't offer a more precise ship date at the moment as we have a lot of technical challenges to work through, rest assured it's…

@Su Wainwright After we introduce the feature discussed in this post my recommendation would be: * Follow the steps in this post for EPIC-FEATURE-STORY. This will apply to all COmpany-managed projects. * Use Team-managed projects for projects that require EPIC-STORY.

@Ree Agarwal Renaming epics will be supported in Free and Standard editions ie. you'll be able to have a 3 level hierarchy (sub-task, story, epic), creating levels above will be continue to be a Premium/Enterprise feature. @Rodolfo Romero - Adaptavist Yes this is all on the path to supporting TM projects in Advanced…

@Rodolfo Romero - Adaptavist The use case we're implementing would result in Epic being renamed in all company-managed projects. As a workaround, you could have all the company-managed projects use Feature, and those teams who want to use Epic can use Team-managed projects.

@Sylvain Gautier @Craig Nodwell we haven't released these changes yet, we'll have more to share in the coming months.

@Ree Agarwal when these changes roll out you'll be able to have that hierarchy in place, you'll be able to rename Epic to Story, then create a new level above called Epic. But the constraint of needing to add a parent to the Sprint will not be resolved unfortunately, and it's not on our roadmap to address this. @Mark…

@Scott Theus Supporting multiple issue types at the Epic level isn't in our plans at the moment. Can I please that you add a vote to this public ticket and add yourself as a watcher so that you'll get updates? https://jira.atlassian.com/browse/JSWCLOUD-7203

@Scott Clasen When you create a new level it should immediately go to the top, in the screenshot above it would be called Level #2. Then add the issue type Initiative to your newly created level.

@Mark Thompson we'll get that uploaded as a Community blog shortly as well which will have comment functionality. Please feel free to create a support request as well if you have specific concerns we can help with.

Hi @Ulrich Kone this functionality hasn't shipped yet. We have recently shared more details about our plans, you can find them here https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/

Hi all, thanks for your feedback. There were a lot of questions here about epic-link behaviour, so we've created a dedicated post to answer your questions in more detail over here https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/ @Leigh-Ann Barnard please note that…

Hi All, there were a few questions here about epic-links and parent-links so we've spun up a dedicated page to answer your questions in more detail: https://support.atlassian.com/jira-software-cloud/docs/upcoming-changes-epic-link-replaced-with-parent/ @Guy Anela Please note that these changes haven't rolled out yet.

@Craeg Strong yes that's right, we are aiming to support customers implementing a SAFe issue hierarchy. We also want customers to use the taxonomy that works for them whatever framework that may be, we've found there's a lot of value in this for non-technical teams as well. You can see more…

@Bryan Darr this blog covers our plans for Epic fields in more detail: https://community.atlassian.com/t5/Jira-Software-articles/Upcoming-changes-to-epic-fields-in-company-managed-projects/ba-p/1997562?utm_campaign=&utm_content=post&utm_medium=email&utm_source=atlcomm#M655 TLDR: We will switch to using the Issue Status…

@Mark Thompson We'll share a more accurate timeline as we get closer to the release, we're still a while away from that so I'm unable to give you a specific date at the moment.

@Ian Rees For now, we will continue to support only a single issue type at the traditional Epic level of the hierarchy, but you'll be able to rename that issue type to your choice of term.