Petter Gonçalves Atlassian Team

Hello @Connor Hogan Thank you for reaching out. The time that the issues will remain in the done column of a board and how you can change it depends on what board type you are using (Classic or Next-gen) and what methodology you have applied to it (Scrum or Kanban). Allow me to provide you with possible scenarios: * In…

Hello @Tina_Allen Thank you for reaching out. It is expected that the field Organizations are not displayed in sub-task issue types since sub-task issues can not be displayed in the customer portal of Jira Service desk. Allow me to provide more context about this behavior: As you can see in this documentation, the…

Hello @Ashwani_Sharma Thank you for reaching out. Unfortunately, it is not possible to set project permissions (Create issues, delete issues, etc.) per issue types. We have already requested this ability with our development team before, however, they decided not to implement it since it would add more complexity and…

Hello @Scott Mason Indeed, it is n expected behavior that some elements of the new UI takes a little longer to load than the background of the page, however, it should not take more than 5 seconds to fully load the page. That being said, allow me to bring you some concepts and question so we can confirm we are on the same…

Hello @Ines Büntig Thank you for reaching out. Unfortunately, it is not possible to configure a specific single field to be editable or not in Jira Cloud. We understand how useful this functionality would be for some customers, so we created the following feature request to consider its implementation: Allow a specific…

Hello @Kory Cunningham Welcome to the Atlassian Community. By default, the context of the Story points field is only applicable to Stories and Epics, not bugs. This is an intended configuration of JIRA, as explained in the documentation below: - Configuring estimation and tracking That been said, you can change the custom…

Hello @Felipe Guerrero Can you please ask her to provide a screenshot of the options that appear when she tries to Split issues? Additionally, ask her to check the steps below: * The option to Split an issue is only available for Classic projects, so make sure that you are not testing in a Next-gen project * , Try to add…

Hello Craig, Thank you for clarifying your request. I completely agree there are some features missing in the new issue view and that's why it is still a lab feature that can be turned on and off in the application, where our developers are still working to get it fully implemented. That being said, I believe there was no…

Hello @Doug You are welcome! The type of project is Next-gen and can be easily identified when you navigate to the project, while the template (Scrum vs Kanban) depends on which features are being used on them. In fact, Next-gen projects can be even used with features of both methodologies (Scrum and Kanban), so when I…

You are welcome, @Panagiotis Liapis Have a nice day and let us know if you have any other questions.

Hello @Chris Shaffer Thank you for your answer. Actually, the issue security levels were implemented a while ago in the New issue view of Jira. The suggestion I mentioned before was successfully implemented for Classic projects: - Jira New Issue view does not display the Security Level of an issue To configure security…

You are welcome, @Muhammad Umar Hanif Let us know if you have any other questions.

Hello @Doug Thank you for reaching out. Both Scrum and Kanban templates of Next-gen projects have the exact same features and possibilities. Practically, the only difference between one template and another are the features initially selected for each of them: Scrum: Kanban: In Scrum, your work is defined by Sprints and…

Hello @Ivan Nicola Sini Thank you for reaching out. Indeed, I believe that your rules can be implemented using the new Automation for Jira functionality under Project settings > Project automation. In order to confirm what exactly you need and that we are on the same page here, please allow me to go further on each…

Hello @Panagiotis Liapis Sorry to see you are facing this problem. Per your description, it seems your client is facing the mentioned error only in an issue level, but he is able to navigate in the application and related project. Is that correct? Just to confirm, is the user added as a standard Jira user or as a customer…

Hello @a_bondarchuk Welcome to the Atlassian Community! Per your description, I understand that you applied the same settings from another project to a newly created project, however, this caused the board of your new project to order issues in a chronological way instead of keeping them displayed by priority as it was…

Hello @Muhammad Umar Hanif Thank you for reaching out. Per your description, I believe you would like to schedule/set the business hours and days of the Time tracking fields (Time spent, Original and Remaining estimate) for specific months in Jira. Is that correct? Unfortunately, it is not possible to change the business…

Hello @YJ Huang Thank you for reaching out. Indeed, I believe you can find the information you need by using Jira REST API or CSV export. In order to better understand what information you exactly need and confirm we are on the same page, please allow me to go a little bit further on each request: 1 - List of projects…

Hello @walter Thank you for your reply. Can you please provide us a screenshot displaying how you are trying to add multiple Stories to your Epics? I want to confirm what is the view you are using to link your Epics so I can also reproduce the behavior you are facing. Additionally, I believe the "Epic button" you saw in…

Olá, Andre. Obrigado pelo seu retorno. Pela sua descrição, eu acredito que você quer retornar a seguinda informação na mesma query: * Todas as tarefas do projeto "WMS Service Desk" que estão na organization "Friozem" * Todas as tarefas do projeto "WMS Legado Bugs e Customizacao" que estão na fixed version "3.13.0.0" Para…

Hello @Brian Oconnell Actually, all the topics of that documentation are also applicable to Jira Cloud application, however, I was able to find a version for that KB for Cloud, which have some more specifications: Mentions and Autocomplete are not working in JIRA Cloud 

Hello @asaf alon Welcome to the Atlassian Community! In order to know we are on the same page here, please provide us with the following information and try the following steps: * What kind of alert you are trying to send? Specifically, what is the trigger of the alert (Issue create, issue edit, etc)? * Are you logged as…

Hello @Tyler Johnson Thank you for reaching out. Unfortunately, the Automation for Jira Cloud does not support the people field of Next-gen projects. In fact, Jira next-gen have different custom fields from classic projects, which are treated as unique identities on each project and are not mapped in the Automation for…

Hello @James Malgieri Thank you for reaching out. Per your description, I understand you are struggling to identify a common field to properly check which issues should be linked to another in two different instances. Is that correct? Indeed, there is no way to know what issues should be linked to another if there are no…

Hello @Jiri Bures Thank you for reaching out. Indeed, I believe it is not possible to prevent only public comments to be posted on transition screens, however, it is possible to prevent any kind of comments to be done in a transition screen by using workflow properties. These would be the steps to fo it: * Navigate to your…

Hello @fernanda.noe Welcome to the Atlassian Community! Per your description, I understand you would like to see a report that provides the estimation and time spent of each sub-task in a Sprint. Is that correct? You can use the filter results gadget to have this information on your dashboard. These would be the steps: *…

Hello @Joey Thank you for reaching out. Per your description, I understand you want to break down your process into multiple hierarchies, where your issues would have 3 phases with 7 tasks on each phase. Is that correct? Analyzing the scenario you are trying to achieve, I believe the use of Epics and Sub-tasks issue types…

Hello @[deleted] In order to ensure all the steps of the documentation provided are checked and further troubleshoot the problem, we need your administrator to provide what results exactly he got from each step of the troubleshooting documentation. More specifically: * Ask him to provide a screenshot displaying the results…

Hello Everyone, We have a quick update about this thread: Due to the implementation of the new European General Data Protection Regulation (GDPR), the parameters used to identify users in REST API as "username" and "userKey" were replaced by the Atlassian account ID (accountId). You can find more information regarding this…

Good to know you were able to solve your issue, @Rafa Paz Let us know if you have any other questions and have a nice day!