Petter Gonçalves Atlassian Team

Hello @Catherine Blieka Thank you for reaching out. The batch notifications are set by default in Jira Cloud. Hence, you should have the batch notification enabled already from your Jira Cloud. Can you please let us know if you facing a different behavior? Additionally to that, we have created a feature request and a…

Hello @James Muir Thank you for reaching out. Per your description, I understand you would like to add a custom field only to a specific issue type, not displaying this field in other issue types of your Jira site. I believe the best way to achieve what you need would be to add the custom field ONLY to the screens related…

Hello @Yaron Azar Thank you for reaching out. Per your description, I understand you are trying to transition the Story (parent issue) by dragging and dropping directly on the board when all the sub-tasks are done. Is that correct? Checking your screenshot, it seems your board is configured with the Story swimlane. It is…

Hello @Josh Evans Thank you for reaching out. Unfortunately, it is not possible to define which issues are displayed in the backlog of Next-gen boards. This happens because the simplest architecture of Next-gen does not allow the editing of the board filter or the mapping of status in the board columns, as you can do in…

Hello @Jacob Lusco Thank you for reaching out. Per your description, I understand you would like to reference the organization field with a smart value in an Automation rule. Is that correct? Can you please provide us a screenshot of your automation rule (Hiding any sensitive data) so we can have more context on how you…

Hello @Mackowiak Thank you for reaching out. Unfortunately, Jira automation does not have a smart value to add an attachment value to the e-mail notification action. The only available smart values for Attachments are the ones listed in this documentation: * filename {{attachment.filename}}: the filename of the attachment.…

Hello @Subbu Ravi Welcome to the Atlassian Community! Unfortunately, Jira Cloud application does not have a dynamic Custom field in which values could be based in an External Database. In fact, this feature was already requested before, however, due to possible performance issues and the low number of requests, we decided…

Hello @JJ Thank you for reaching out. Checking a few details of the automation and executing some tests, I noticed that the automation for creating requests does not accept the summary field to be blank, even if you have added a default value in the request type. To confirm if that's the case, please try the steps below: *…

You are welcome, Nick! 

Hello @Day_Reynolds Thank you for reaching out. Can you please let us know if you are using a Next-gen or Classic board? Also, which is the view where your cards are displaying exactly? Can you provide us with a screenshot? If you are talking about the Backlog and Active board views of a Classic project, you can change the…

Thank you for confirming @Sara Let us know if there is anything else we can help with.

You are welcome @Nancy Bonanno Have a nice day!

Hello @Chetan Singh Thank you for reaching out. Unfortunately, it is not possible to share the same custom field (From a Classic or Next-gen project) between multiple Next-gen projects. This behavior happens because the architecture of Next-gen projects was designed to use unique entities (Fields, issue types, statuses,…

Hello @Nancy Bonanno Thank you for reaching out. Per your description, I understand you want to add an approval step in the workflow of a non-service desk project, however, you are not being able to set the permission to view and transition the issue to the assignee (Manager) in the approval step. Is that correct? Please,…

Hello @Kk Welcome to the Atlassian Community! Per your description, I understand you are trying to migrate a Jira Service desk Server to another instance, keeping all the Service desk data during the process. There are some key details you must have in mind to know what would be the best approach to achieve your goal: *…

Hello @James Pickard Thank you for reaching out. Per your description, I understand you would like to add a select list field to the resolution screen of your issues that will list the three pre-determined options you mentioned. Is that correct? It's quite easy to create a select list field with the pre-determined options…

Hello @Sara Welcome to the Atlassian Community! Can you confirm to us if the project you are specifying in your JQL query (DEV) is a Next-gen project? If that's the case, we have reported this behavior as a bug to be fixed with the Next-gen API: Unable to search for subtasks when filtered by sprint Feel free to vote and…

Hello @Jordan Berkley Thank you for reaching out. Per your description, I understand you are trying to search for Stories based in a custom field of their related Epics. Is that correct? Also, The JQL syntax you provided (issueFunction) is not related to Jira JQL functions itself, so I believe you are using a third-party…

Hello @Shannon Griffin Welcome to Atlassian Community! I'm not sure if I understood what exactly you are trying to achieve, but it seems you are trying to import issues through CSV as sub-tasks of other existing issues in your Jira site. Is that correct? Please, allow me to provide you with some concepts and ask some…

Olá @Henrique Degan Poderia nos informar qual o erro retornado? Visto que o sumário é adicionado de forma explícita no JQL, acredito que o mesmo não aceita caracteres especiais.

Hello @Jovita Mathias Welcome to the Atlassian Community! Per your description, it seems the process to estimate and track your issues with Story points is correct, so I believe it must be a problem between the Story points field and the reports. Please, check the steps and questions below to properly troubleshoot the…

Olá @Henrique Degan Vi que você conseguiu fazer a regra que eu mencionei. Ela funcionou conforme esperado?

Hey James, Thank you for the provided details. I'm glad to know you were able to identify what caused the confusion with the creator field. If there's anything else we can help with, please let us know.

Olá @Henrique Degan Bem-vindo a comunidade Atlassian. Pela sua descrição, eu entendo que você quer configurar uma regra de automação para automaticamente criar um link do novo ticket criado para todos os outros que tenham o mesmo sumário. Correto? Você pode criar a regra seguinte para ter esse resultado: O.B.S: O campo…

Hello @muneet.bakshi Thank you for reaching out. Indeed, The CSV import to Next-gen projects doesn't respect the mapping of the Issue type field. We have a bug reported to fix this behavior: CSV imports do not map Issue types for Next-gen Feel free to vote and watch the bug to increase its priority and also receive…

Hello @Erik Goodman Welcome to the Atlassian Community! Per your description, I believe you might be missing some step of the process to integrate Github and Jira Cloud application. Please, allow me to provide you with some concepts so we can know we are on the same page here: The integration between Github and Jira is…

Hello @James Malgieri Thank you for reaching out. Per your description, it seems you are trying to change the creator of your Jira issues when importing them from a CSV file. Please, allow me to provide you with some context so we can better know we are on the same page here: The Creator system field is used to identify…

Hello @Devany Cocco Thank you for reaching out. Per your description, I understand you are trying to automatically add a comment when an issue is assigned, adding the comment with the name of the user that is assigned to the issue. Is that correct? I'm not sure if it is possible to do with workflow post functions, but you…

Hello @Rick Measham That's really strange behavior. In fact, the screenshot you provided is slightly different from the Old View itself. Digging a little bit more about this, I believe you are facing the following bug: Old issue view is shown when clicking the issue link in the list view To confirm if you are facing this…

You are welcome, @Dom Thank you for letting us know that it has properly worked for you. If you have any new questions, please don't hesitate to contact us again. Have a nice week ahead!