Kevin Bui Atlassian Team

Hi @Priyanka - is it possible that the epics in the epic panel were all marked as Done, like in the screenshot below? Epics marked as Done in this way disappear from the epics panel, but can still be found using JQL or in the Epics report. 

Hi @four zhang - Welcome to Atlassian Community! If you want to try Jira, you can sign up for a trial on the Jira website (select the Try for free button). For more tips on how to get started, check out this getting started guide.

Hi @Christina Kyriazi - if I'm understanding you correctly, what you want to do is: * (if you haven't already) Create an account for your marketing team's email, and add them to your Jira project. * Navigate to your Jira project, and select Project settings > Details. * Under Default Assignee, select the account you…

Hi @Francis_Pelland Any thoughts on how that "FALSE" value can be removed? I wish I could be more helpful, but the only thing I can recommend is contacting Atlassian Support, who will be able to take a closer look at your Jira Cloud instance. There's no way to configure locked fields, so I'm not sure what else you can do.

Hi @Francis_Pelland - I'm not really sure what to make of that. The Flagged field should only have one value, Impediment. And given that the field is locked, I don't know how other values could be added to it. Do you know of any Marketplace Apps installed on your Jira that could have added the value?

Hi @Francis_Pelland - Some fields in Jira are marked as LOCKED to prevent changed to the field that could accidentally break the way Jira works. This often happens with plugins where certain custom fields are crucial. This seems to be the case with the Flagged field.

Hi @Kim , In next-gen Jira Software, the default issue types are Story, Task, Bug and Epic. To configure a Risk issue type, you'll need to add a new issue type: * Navigate to your next-gen project. * Select Project settings. * Select Issue types. * Select Add issue type. Hope that helps!

Hi Daya - We do have a guide matching Scrum concepts with Jira functions, which you can view here. You can also browse the Agile Coach website, which has various other guides related to agile and Jira.

Hi @Gysbert - As far as I know, time tracking capabilities are on the team's radar, but I can't confirm that they're working on anything specific in this area. You can check out what's being worked on for next-gen at the Jira Software Cloud public roadmap.

Excellent! Glad I could help.

Hi @Raj R , In my experience, using 2 different Jira instances across 2 different teams is not uncommon. Different vendors will often prefer to use their own Jira instances for various reasons (eg; maybe their instance is configured the way they like it, or maybe it has add-ons that they use, etc). I would say the main…

Hi @Sigurd Saue, I'm not sure if this is viable for you at all, but one option I can think of is to plan and start the sprint from MASTER, and then use Quick Filters to swap between SUBA, SUBB, SUBC, and SUBD. But for this to work, SUBA, SUBB, SUBC and SUBD would have to be labels or components, rather than boards. Hope…

Hi @jmodena Reports in Jira Software (including the Burndown Chart) are generated based on the board's filter. So if I'm understanding your question correctly, what you want to do is: * Create a new JQL filter that contains the subtasks and programming tasks you want to report on. * Navigate to your project in Jira…

Hi @Gysbert , When you say "next-gen projects", are you referring to next-gen Jira Software projects? If so, you're right that time tracking functionality is quite limited. For now, if you do need more thorough time tracking capabilities, the only thing I can suggest is to use Jira Software's classic projects instead.

Hi @dayanidhi_naidu , From your board you should be able to open an epic and select … > Move. Here's a GIF of what that would look like for more context:

Hi @[deleted] I have shifted to JIRA Epics being “features” to encompass the overall body of work and decomposing the user stories leveraging sub-tasks for internal team and tasks for external team. My thoughts are that the subtasks are prerequisites for the closure of stories. I think this is a viable way of looking at…

Hi @Ismail Alami In next-gen projects, the DONE column (ie: the very last column on the right) is also the resolution column. Any issues moved to this column are automatically set as "Resolved" (also, issues that leave this column lose their resolved status). Could you please provide more info on what you mean when you say…

Hi @Jira Service Desk - You can create classic projects by going to Jira home > Projects > Create project > Classic project. If you're unable to create a classic project, it's because you don't have the right permissions to create one. You'll need to ask a Jira admin to create one for you (which has always been the case;…

Hi @[deleted] - My understanding is that all issues in the classic project will end up in the backlog. From the doc you've linked: Active sprints: Sprints in progress in your classic project won't move to your next-gen project. Issues that were in the active sprint in your classic project will be in the backlog of your…

Hi @Laura Bowers - At the moment, the only two reports available in next-gen projects are Burnup and Velocity, so there's currently no epic reporting like what you're describing. However, this is definitely on our radar. I can confirm we have more advanced epic functionality in the works for next-gen projects, including…

Hi @Pedro Jaramillo - That's really cool! I love seeing people use Jira in unique and unusual ways. Would love to see more about how you're using it once you're further in to your journey.

Hi @Kereshmeh Javaherian - You can find a quick beginner's guide to Jira here: https://www.atlassian.com/software/jira/guides/getting-started/basics. Happy to point you to more resources if you're looking for something more advanced. Good luck!

Hi @Allen Earman - As @Jack Brickey said, next-gen projects currently don't have a Workflows option. In next-gen projects, the workflow is your board, and your board is the workflow (for now!). The documentation you're following is probably for classic projects.

Hi @Rach - Next-gen boards can currently only have one column where tickets fall off the board (this is always the last column). This means that it isn't possible to have both a DONE and a CANCELLED column. The good news is that this level of column and status management, where you can have multiple statuses on your boards…

Hi @George Singletary - As far as I know, there is no way to migrate next-gen story point estimates to classic projects.

Hi @Shaurya Gupta - There is currently no way to archive done cards on a next-gen Kanban project. Cards will automatically be cleared from the board when they remain in your Done column for 14 days.

Hi @Trevor Loveland Thanks for bringing this to our attention. I've fixed up the screenshots on this page, so that they are now up to date. Cheers, Kevin Content Designer, Jira Software Cloud

Hi @Jay Keck - We've been slowly rolling out subtasks to next-gen projects over the last few weeks; looks like you were one of the lucky ones who got it early! You can read more about Subtasks in next-gen, and where the feature is heading, in our Community announcement article.

If you're working in sprints, you'll need to: * Create a new sprint * Move issues from the Backlog section to the sprint * Start the sprint

Hi @Gabriel_Melo - The Backlog page on your next-gen Kanban project has two sections - the Board section, and the Backlog section. To make issues show up on your Kanban board, drag them from the backlog section to the board section and they will appear in their respective columns. Hope that helps!