Walter Buggenhout Community Champion

Checked in with Atlassian and it seems it was indeed a change. Apparently, it has been rolled back by now. If all is right, after refreshing you should be back to normal.

Hi @Inna S, 2 things here: status categories are: * to do (grey) > means no work has been done yet and issue waits to be started. * in progress (blue) > means an issue is actively being worked on. * done (green) > means no work is to be done anymore. You cannot extend that list. However, Jira has the concept of resolution…

Hi @Jaime Basco and welcome to the Community! In essence, every project can act as a template - as long as it is a company managed project. When you create a new project, after selecting an existing template and taking some extra steps, you will end up on the screen where you are expected to enter the key and name of your…

Hi @Roman Polyanskiy and welcome to the Community! Several people in the community are currently reporting this behaviour. So it looks like a more global issue or change.

Hi @Darwin Valencia and welcome to the Community! Several people in the community are currently reporting this behaviour. So it looks like a more global issue or change.

Hi @Anuradha Muddana Several people in the community are currently reporting this behaviour. So it looks like a more global issue or change.

Hi @[deleted], I totally agree with you on the continuous deployment statement. Apart from tooling, in that same, continuous deployment scenario it does not make much sense to include all your (technical) releases on a roadmap either. A roadmap is meant primarily to visualise the key milestones (such as MVP releases or…

Hi @Stephen Yang and welcome to the Community! You are trying to do something that is not what the product is designed to do. The group by function in advanced roadmaps does exactly what you describe: it displays a group for every single label (in this case) it reads from the issues in your plan and then displays all the…

Hi @[deleted] and welcome to the Community! My best guess is that you assigned start and end dates to your issues (either on the issues individually or by adding them to a sprint) and that the version you added them to has different, conflicting start and end dates. You can check that by comparing the start/end dates of…

Hi @Ka Silveira, Ideas are a feature from the very new Jira Product Discovery product, which is currently in beta. Discovery project are team managed only, which means that the idea issue type is not shared globally across Jira. And that is why you can't add it to the hierarchy. There are currently some known limitations…

Hi @SCF and welcome to the Community! I am not sure if I understand your question correctly. But it seems that you are confusing projects with boards. If not, feel free to correct me; When reading your question, it looks as if you are looking to track different initiatives (I assume you mean actual projects) in different,…

I just came to realise it doesn't have to be that complicated: 😎 First Jira Software, Then came Service Management, Now Work Management

Hi @Paulina Carvajal Muñoz, Yes, you are correct. The Project Management project is a business project (Jira Work Management), while Epics are a Jira Software feature. You can indeed add the issue type to a business project, but the hierarchy of issues is not foreseen there. Hope this clarifies!

Hi @Gregory Kremer and welcome to the Community! If you're not going to copy any data, doing it manually will probably be the fastest option. 

Hi @Вікторія Процюк, That is because there is a value in the resolution field on your issue. That means the issue is completed and no more work is expected to be done on it. Hope this helps! 

Hi @Elif Meriç and welcome to the Community! Maybe your assignee group field is not present on the create screen of the issue type you are trying to create. That may also be a possible cause. Hope this helps!

Ok; then issues should automatically disappear from the board 14 days after they were closed. If you are working so fast that even then your done column gets crowded, you should be able to manually remove them with this menu option: Notice that this screenshot is from an actual kanban board in the project, displaying…

Oh no! Depending on the type of project you are using and the board configuration, they just vanish automatically from the board after some time or as part of a process. To give you a proper answer here: are you talking about a business or software project? Team managed or company managed?

Hi @Nicolas VanOrten and welcome to the Community! While archiving individual issues is an option on the Data Center version of Jira, it currently isn't on cloud. You can archive full projects, but not individual issues. There is a - pretty old - feature request for this, that you can track here: JRACLOUD-5843. Hope this…

Hi @Melle van Keulen, The basic hierarchy in standard Jira is Epic > Task > Sub-Task. When planning sprints, it is issues at the Task level that are actually being added to the sprint (sub-tasks are included automatically) and issues at the Epic appear in the Epic panel on the left hand side in your backlog, where they…

Hi @Angus and welcome to the Community! Basically: find the integration that is sending the notification and disable it. This may be a Slack integration in a project, an integration through Halp or an automation rule linked to your project or site. Hope this helps you get underway!

Hi @Yuxuan Li and welcome to the Community! No, JQL does not impact the fields it returns - it just executes a search commands that returns a list of issues. In the Jira UI, you can select the columns displayed in the filters > advanced search screen. If you want to query via a webhook, you'll need to specify the…

Hi @Vivek, You cannot create conditional fields, but you can configure the screens for your issue types differently so they display the fields you want on them. In company managed projects that requires quite a few steps: creating screens, screen schemes and screen issue type schemes to link everything together. You can…

Ok, when you want to indicate an issue is blocked, the best way to deal with that is by setting a flag to your issue, as @Dave Mathijs mentioned. On your scrum/kanban board, right click the issue and select the option add flag. The card will be highlighted in bright yellow and get the icon of a tiny red flag on it. When…

Hi @Sunilkumar k, You can use card colours on a board to set a colour to an issue card if your issue meets certain criteria. But you'll need to be more specific about what you are trying to achieve here: * what do you mean by "the issue is in conflict". With what? Being overdue? Having more time spent than originally…

Hi @Maria VanderMeersch, Permissions on a set of issues can be set easiest at project level. If someone has only browse project permission in a project, he/she will only be able to view all issues in that project. If you want to restrict permissions on a sub-set of issues in a project, that can be achieved with issue level…

Hi @Frances M., If you are an admin for your site, you should be able to accomplish this by following the steps in this support article. Hope this helps!

Aha, thanks for the screenshots, @Pablo Diorio. This is a Jira Work Management board. Your issues in the done column only remain visible there for 14 days after they were closed. After that, they sneakily disappear indeed: You can still view them from the list, timeline and calendar views. Check out the docunenntation for…

Hey @Krista Dyer, That question goes a bit beyond just projects and boards. A common (best) practice is to create a project with a shared configuration with another project. It is a step that you can select after you selected basically any template and get to the point where you enter your new project's name and key. That…