Eoin Atlassian Team

We've confirmed with @Ben Sullivan that this works with the transition rule

@cokefour are you a project administrator for the next-gen project?

It's possible to * Add the "Time tracking" field to an Issue Type in next-gen Project settings. * Log time and Time remaining from the Issue View * Have logged time show up in the Worklogs We have not yet built the time tracking report although it will be something we make available in the future... most likely 1+ year…

It's possible to * Add the "Time tracking" field to an Issue Type in next-gen Project settings. * Log time and Time remaining from the Issue View * Have logged time show up in the Worklogs We have not yet built the time tracking report although it will be something we make available in the future - most likely 1+ year time…

You are definitely not doing something wrong :) If the work isn't done, and you don't want it hanging around in the backlog - how about moving it to another project? There is a Move option in the issue meatball that you can could use - note this has a few steps involved so it is not currently very efficient. Alternatively…

I've just tested it myself on my production instance and it works for me @[deleted] - I could do a quick screen share with you to have a look around with you on your instance if you like. Email me at eryan@atlassian.com

@Ben Sullivan There are some preconfigured transition rules that you can use inside the workflow editor - on the transition from In Backlog to To Do, you can use the "Update an issue field" to set the current date inside the Start date field. It might be easier in this case than using the automation engine. You can…

Hi @Nick Maskell - it's not possible to hide tasks one by one at the moment. It is something we will consider for the future but it's currently not a high priority based on overall feedback. If you are working in more of a kanban style (i.e. no sprints) you can archive all tasks in a Done column at any time. You can use…

Hi @Ravi Mistry - it's not possible to have a mandatory field on issue creation in next-gen projects; however it is possible to create a workflow rule to check a field has been populated on transition to another status "Check an issue's field"…

@fabian you can query on next-gen epics using the parent =. If you want to combine Epics from both project types, an example of such a query would be: "Epic Link" = NPC-6 OR parent = NJDP-5 The Parent field can also be selected as a column in the Global Issue Navigator and exported from Jira.

Also if the issues are in the Backlog container on the Backlog view (i.e. not the Board container) they will disappear immediately if there are marked as Done.

Hi @Edwin Scott - it's not something available in next-gen projects yet unfortunately (it is available in classic projects). There is an order which is created upon status creation - so one possible (painful) workaround you could use is to recreate all your columns in the order you want - and then delete the old columns…

@Daniel Schultz Nielsen you may find providing stakeholders outside your team with a saved filter may also satisfy your needs. It is similar to the above (but above you would need to go one step further and create the board using the filter - which would allow you to show the issues on a Backlog view). The support doc for…

@JAKE @Daniel Ebers @Pramodh M this is the feature suggestion to follow for having a dedicated workflow for epics... https://jira.atlassian.com/browse/JSWCLOUD-17434 We have a team actively working on it! Thanks, Eoin Product manager

Hi @Tim Kras . We're sorry this doesn't meet your needs and it is something we are considering in the future. The Board within next-gen represents active work and we opted for automatic clearing as a first step to help reduce noise on the active work view, which was the desire from the majority of people. The "Issue…

@Vadim Rutkevich I've set up some time for us early next week. Looking forward to chatting with you!

@Kevin Lannen We'll be monitoring usage and impacts on other behaviours to ensure people are getting value, and this will help inform expanding this approach to other parts of the product.

Hi @jesse.griffith - great to hear you are excited about these changes! I won't rule out this coming to classic at some point in the future but there are no current plans to do this. You'll be glad to hear that estimating in hours is next up for my team and we'll be looking forward to welcoming you and your team to the…

Cheers all for a fun discussion :) I believe estimation is a great way to gain a shared understanding in a team and it can bear fruit to many productive conversations that can help a team deliver value more efficiently. However it's unfortunate it can also cause anxiety for people when it's mis-used / over-used. The latter…

Hi @Andrew Dunne ! Up to now, we have been focusing on making next-gen a great experience for the single team use case. Although great news is we are soon going to be switching our focus to the multi-team use case like the one you have described. It is possible in the short to add team name as a label to each issue - and…

Hi @Rene Davis Yes this is possible. Here is some documentation to help out... https://www.atlassian.com/blog/jira-software/github-for-jira

@Dan H @Sebastian Obentheuer thanks for your feedback - we'll move the panel to be driven by local browser storage rather than being a URL parameter. We're going to start working on it soon. Cheers, Eoin

This should now be available @Sergio Jivan ! https://community.atlassian.com/t5/Next-gen-articles/Improved-Backlog-planning-in-next-gen-with-the-epic-panel/ba-p/1387675

Thanks @__ Jimi Wikman - we're really looking to enable teams use epics in a way that best suits their circumstances (and for a lot of teams that means not even calling them epics). I'm assuming your questions are about work structure/hierarchy more broadly in next-gen as opposed to the efficiency improvements on this…

@Johannes Schneider we are currently rolling out a new panel in the Backlog. You can toggle it from the epic filter dropdown. And it will you to drag and drop issues from your backlog onto a specific epic. Let me know if you don't see this toggle on your instance by tomorrow.

Hi @peter.casey - we are rolling it out at the moment. I can have it turned on for your instance if you want to send your instance name to eryan@atlassian.com - thanks!

@Dan I don't believe anyone has raised a feature request specifically on this yet, however we do have a lot of interest for a summary field at the parent level. We have just recently rolled out displaying the story point estimation badges on the child issue cards in the issue view. Have you found this useful?

Thanks for flagging this with us @bwebster - we'll take a look

@Jocelyn Ramirez when the grouping is mage available as a setting that everyone can use, this will allow some people in your team to view the Board grouped by subtasks and other to view the Board grouped by stories

Good to hear you nothing serious has gone wrong. This is an area that has caused confusion so you are not alone. We need to improve how we tell people where the newly created issues are going, and maybe in the longterm given an option as to where it should go.