Angélica Luz Atlassian Team

Olá @Willyan Luiz Genaro Seu email estava bloqueado pelo seguinte erro: 550: 550 5.4.1 Recipient address rejected: Access denied. AS({hex}) [SN1NAM02FT0061.eop-{base64} {hash}:50:36.474Z {hash}] Eu removi esse bloqueio e as notificações devem ser entregues normalmente agora. Atenciosamente, Angélica 

Hi @Marcelo Ignacio Cid Abud, It's possible to export the list of customers directly via User management. For these steps, it's required to be a site-admin: Old experience: Cog icon > User management > Jira Service Management > Export customers. New experience: Cog icon > Products > Select your site under "Sites and…

Hi @Yanko Chakarov , Welcome to the Atlassian Community! In order to approve or decline a request, it's necessary to do it via the Buttons that appear on the ticket, so it won't be possible to change the status via the Queue. What will trigger the status change is the Approve or Decline buttons, so it's necessary to access…

Hi @Elaine McMillan, This workaround only works when using User Picker (single user) custom fields. Regards, Angélica

Hi @Charles Gage Thank you for reaching out to Community! There are no issues in changing the name of the Organization and it won't affect any access or integrations. It's exactly as you said, it's a "convenience name" that will appear on the top of the page and also a name that you can easily identify when you access…

Hello everyone, Hope everyone is safe! It has been a while since this question was posted and the workaround I shared required one If/Else for each property, but that's not necessary anymore. There is a smart value that gets the value from the property and adds it to the read-only field.…

Olá Rafael, Nesse caso em específico o Relator do ticket também estava como Watcher e quando isso acontece, as notificações internas (sistema) são prioridade, por isso a notificação de CSAT não estava sendo enviada ao Relator por ser uma notificação para cliente (externa). * What notifications do my customers and team…

Hi @Christian Happel Thank you for reaching out to Community! It's possible to remove the permission to create tickets on a specific project, but it would affect all customers, it's not possible to restrict a few ones. Other than that, if you want a project where people need only to view the articles and not create…

Hi Diogo, Welcome to Community! We would need to better investigate the issue to understand what is happening. We had an incident this week that affected several types of notifications: * https://jira-service-management.status.atlassian.com/incidents/0f19gmg91n91 If you are still experiencing this issue, please reach out…

Hi Jordi, The issue Robert was facing back in 2019 was related to a bug that was already fixed. * Initialed avatars missing for users without avatar on instances with SSO enabled If you are facing a similar issue, it might be related to another setting. Feel free to raise a new question and please, share a screenshot (just…

Hi @Alexandra Wolff Thank you for reaching out to Community! Testing on my local instance, the Expand macro is now collapsed by default. I tested using the Confluence page on the new editor. Can you please test to see if the page you are viewing is using the new or the legacy editor? If it's the legacy editor, we suggest…

Olá João, É possível desativar somente a notificação de alteração de status. Essa alteração também é em Configurações do projeto > Notificações de cliente > Status visível do cliente alterado. Atenciosamente, Angélica

Hi @Javier Barquin, Customers will have the ability to reset their password via the login page, so it's not possible to prevent them from doing this. Regards, Angélica

Hi @Nik Shafiq Sirhan, Welcome to the Community! In order to add a custom email to a Service project, you need the following: * Have the Administer Jira's permission. This means that you need to be a Jira administrator (be part of groups like administrators and jira-administrators). * Have a Jira Service Management…

Hi @Emma Liu, The bounce was related to the same error: 550: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuch... - gsmtp The…

Olá @Ailson Alves Pereira Obrigada por entrar em contato com o Community! Atualmente não é possível alterar o idioma do Widget. Há uma sugestão de melhoria para que isso seja possível: * Ability to change the widget language Você pode clicar em Vote e também em Watch para receber atualizações e ser informado quando essa…

Hi @Estela Cameira, You need to login to https://jira.atlassian.com/ and the option to vote will be available on the right side under the People section. Regards, Angélica

Olá @Leandro Demenciano Costa, Verificando seu email em nossas ferramentas, o seguinte erro retornou: 550: 550 5.4.4 [internal] NULL MX domain does not accept mail Eu removi esse bloqueio, porém caso o problema continue acontecendo, seria importante entrar em contato com o departamento de TI da sua empresa para eles…

Hi @Milton, Welcome to the Atlassian Community! Checking your email address on our tools, it shows bounces due to the following error: 554 5.7.1 [internal] recipient address was suppressed due to customer policy Then, other emails show as delivered and open, so the bounce was removed. If you are still facing issues, let us…

Olá @oracle.paulo.fonseca A opção de compartilhar configurações com um projeto existente precisa ser selecionado durante a criação do projeto e essa opção está disponível somente para projetos do tipo Gerenciado pela empresa. Se você já criou o projeto, não será possível usar a opção pois aparece somente na tela de criação…

Hi @Jan Jaap Wallien, Thank you for reaching out to Community! You can find detailed information and steps to fix the issue in the documentation below: * User cannot be assigned issues Regards, Angélica

Hi @[deleted], The screen is from the Workflow validator in company-managed projects (Project settings > Workflows). * Configure advanced issue workflows * Use workflow validators with custom fields Regards, Angélica

Hi @Nancy Ketchum, Thank you for reaching out to Community! I can see that you are a site-admin of a Premium Cloud site, so please, reach out to support via https://support.atlassian.com/contact/ so we can help you. Regards, Angélica

Hi @NISL Rybarczyk, By going to Cog icon > Projects you will be able to view the type of the projects and if it's team-managed or company-managed. To move the projects from one site to another, you need to go to Cog icon > System > Migrate cloud site. * Perform a cloud-to-cloud migration for Jira If the NCEE-DTS doesn't…

Hi Valerio, This is happening due to the blockers on the list. You need to follow those steps in order to proceed and transfer the products from one Org to another. While you don't remove SSO, domains, API keys, and so on, it won't be possible to transfer the products. Regards, Angélica

Hello @NCEE Rybarczyk, Welcome to the Atlassian Community! It actually changed! It's now possible to move single projects from one Cloud instance to another, but for now, it's available only for Jira Software and Jira Work Management projects. For Jira Service Management it's only possible to move from Server/Data Center…

Hello @Sebastian Freitag, Welcome to the Community! It's necessary to type the hours and minutes on the field. The dropdown still shows 30 minutes, but you can clear it and type the time and minutes you need. Hope this helps! Regards, Angélica

Hi @Valerio Chang, Sorry for the late response here. I disabled the vortex mode on your site and the transfer should work now. Regards, Angélica

Hi @Maria Christensson, Welcome to the Community! The other thread is this one: * Customers can't see attachment in service portal Hope this helps! Regards, Angélica

Hi @Kymbat Daniiarova, Welcome to the Atlassian Community! Checking your email here, there was a bounce due to the following error: 550: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn…