Eoin Atlassian Team

Thanks @Edmond Melkomian - can you send me an email at eryan@atlassian.com and we can try find a suitable time to do a video catchup? 

@Becky Klein it's on the backlog but no timeline around it yet. It's definitely the longer term direction we want to go. Thanks

Hi @Becky Klein - here is the support page on how to create issue types in next-gen projects... https://confluence.atlassian.com/jirasoftwarecloud/set-up-issue-types-in-next-gen-projects-949233753.html It's currently only possible to have one subtask issue type. Let me know if this doesn't help. Thanks

@Rohan Peshkar you can have one subtask issue type in a next-gen project and tou can rename that issue type to be what you want... https://confluence.atlassian.com/jirasoftwarecloud/set-up-issue-types-in-next-gen-projects-949233753.html

All - we're currently working on a fix for this - apologies for the inconvenience. This should be resolved very soon

We will be looking to include an epic burndown chart in next-gen in the longer term. In the meantime there is an Atlassian built integration for Jira and Google Sheets that may help in the short term... https://gsuite.google.com/marketplace/app/jira_cloud_for_sheets/1065669263016 * some more info on this in our…

Thanks for the feedback @Ian Munday. The Backlog and the Board are different lists and currently independent of the workflow. We will be building in automations in next-gen and as you mention this is an example of something that could be automated. We'll also keep an eye on whether this is causing wider confusion. Cheers…

@Luca Orciuolo we've introduced a progress bar in the issue view over the Child issues panel. This is currently using issue count only, and we are investigating making this a toggle for story points estimation as well. Cheers

@Alexander Brooks we're currently resolving a couple of issues when filtering with subtasks grouping is enabled. Is this when your assignees are disappearing? Feel free to email me with some screenshots or with more detail at eryan@atlassian if easier. Thanks

@Becky Klein it can be set by an admin now. We'll look to make this available for all users in an upcoming piece of work. Thanks

Hi @keving - we're currently rolling out a fix for this. It should be resolved now or very soon for you. Cheers

HI @Jessie Cao The subtasks can be viewed in the issue view, and can be viewed on the board when grouping by subtasks is enabled. The grouping is currently an admin setting and we will be making this as a user setting as our next iteration. Hope this helps Thanks

Thanks @Lee Jiaqi - we're on it and will have this resolved soon

@jesse.mcsweeney a subtasks has to have a parent issue always assigned. If you would like to change the parent you can use the Change Parent action in the card or issue view meatball. Let me know if this works.

Thanks @Lars Aalberts for calling that out about the documentation - I have corrected this!

Hi @Paul Coch , we'll be adding the ability to sort subtasks in the issue view in an upcoming piece of work!

@Jason LaCarrubba we're looking to rebuild the create issue screen for next-gen in the medium term and we originally were planning on bundling the assign to epic change with this work - given we have received some feedback around this, including yours, we'll look at the opportunity cost of investing in extending the…

Hi @Rogier Simonis | MKB Brandstof - we'll be looking to iterate on the visibility of and interaction with the parent within the issue view very soon. Send me an email to eryan@atlassian.com if you would be keen on being part of some exploratory testing around this. Thanks 

@Marko can you send me your sitename to eryan@atlassian.com and we'll take a look? For the story points, there is a new story point estimate field that we have created for next-gen projects so you will be unable to use the story points field that you may have used in classic projects. Once you enable Estimation in the…

@Andy Nash we'll look to make this possible in the longer term through a new broader rules/automation solution, although to be transparent this isn't something we've kicked off yet.

Hi @[deleted] . Thanks for the feedback. We'll be looking to make subtasks a user configuration rather than a board configuration as an iteration to subtasks.

@Guillaume Cougard I understand. This isn't possible right now and isn't something we'll tackle in the short term. I'm sorry for the inconvenience this will cause. I hope going forward you will be able to utilise subtasks in the manner that you want.

@Guillaume Cougard Subtask is the default name we have given an issue type that exists at the bottom of the work breakdown hierarchy. And Epic is the default name for the issue type that exists at the top of the work breakdown hierarchy. In between those two levels you can currently have as many issue types as you like…

@sstoeger Subtasks can be used whether you are using the Roadmap or whether you are using epics. In this case, your project will be set up to use two level of work hierarchy.

@[deleted] this will be something we get to but it's not something we are looking at right now. If this is absolutely something you need and are unable to work around it with our Sheets integration for example (where you can easily pull filtered info into Sheets and create reports off it), then the classic projects may be…

@Victor Burgos we're building out next-gen iteratively and up to we've been primarily targeting the single team with more basic needs. You'll be glad to hear we'll absolutely be increasing the power over time, whilst allowing teams to easily scale up and down this power as they need. I didn't quite follow the comment on…

@Carl-Fredrik Arvidson yes we've gone with subtasks being only visible on the board as a swimlane view for this iteration. A further iteration to this will be to make the swimlanes (grouping) a user controlled view rather than a board view for all the team. Our main reason for going with this approach is based on our…

@Mirek Classic Jira gives us a great source of what to build, and we'll look to supplement that with feedback to help understand whether we are building out next-gen in the best way and in the right priority order. And although this iteration of work breakdown seems like a small step in functionality from a user experience…

@Sarah Ryan Yes, we want to allow you to create multiple issue types at the subtask level in the future so something we'll look to prioritise based on the feedback we are getting. Thanks 

Hi @Edmond Melkomian . We've just launched our first iteration of subtasks and we will be iterating on this in the coming months. Ranking subtasks is on the list and we'll be using feedback like yours to help us prioritise what we deliver next so thanks for reaching out. You can find more info about subtasks and what's…