Fernando Eugênio da Silva Community Champion

@Tom Horton The Validator will work as an action during the transition, while the Condition will work as an action before the transition. For example: If you use the Validator, the user will still see the transition to In Progress status, but if the field is not filled in when they try to transition, Jira will display an…

@Adam Benfer You can do this with Jira automations, you just need to use an additional resource to get what you want. Your automation rule needs to be like this: * Trigger > Your trigger * Action > Create Issue* Select the project * Select the Issue Type * Select any other field you want to fill automatically by the rule *…

Oi @Fabiana dos Santos Siqueira , bem vinda à comunidade Atlassian! Para fazer isso, você precisa ter essas issues de diferentes projetos associados por algum tipo de link (campo linked issues). Se você já possui esse vínculo, tente algo assim: * Trigger > Issue commented * Branch > Selecione a opção "Branch rule / related…

@Davi Barros de Lima , bem vindo à comunidade Atlassian! Por se tratar de uma comunidade, a maioria das respostas daqui são de membros não relacionados diretamente ao controle de sites do Jira/Atlassian em geral. Recomendo que você abra um ticket de suporte direto para o time de Atlassian pelo…

@Sheri Widler This is happening precisely because you created an Organization in your service project with all the users in your environment. To remove this completely, you need to delete the Organization by going to: - Access your service project > On the left side menu click on 'Customers' > You will see the Organization…

@Tom Horton Wouldn't it be better if you put a Validator in the workflow indicating that the 'DB Name' field is mandatory for when the issue goes to In progress? Thus, the user who is making the transition will receive an error message and will not be able to send it to In Progress without filling in the field. I think…

@Mateus Luiz Gonzaga Para conseguir filtrar comentários somente públicos você vai precisar dar um GET via API usando o formato de Customer Request e não de issue como é o comum. Você deve passar o seguinte formato de URL: https://URL DO SITE.atlassian.net/rest/servicedeskapi/request/ISSUEKEY/comment?internal=false Se você…

@Gustavo Reginato , bem vinda à comunidade Atlassian. Este erro pode estar relacionado a diversos fatores relacionados ao projeto ou ao campo que você está tentando filtrar. Algumas possíveis causas podem ser vistas aqui: Jira throws "user exists but has no unique key mapping" on login, or throws "The JIRA server was…

@Mateus Luiz Gonzaga A ideia é fazer um filtro disso em uma JQL do Jira ou usar esse filtro em um API Request? Se a intenção for fazer em JQL, isso não será possível. O recurso nativo de JQL do Jira não se estende a esse nível de granularidade.

@Shaghayegh Khodaeian Welcome to the Atlassian Community! If all SLAs were paused, then they must have the Pause SLA setting in common. Check the cause by going to: Project Settings > SLAs > Expand the SLA you want to analyze and see what is defined in the "Pause conting time during" section. If the SLAs have indeed…

@Kristopher Anderson Honest question here: If the field is multiselect, why don't you define the field where you are creating the issue and select "Copy from Trigger Issue", then the field values will be automatically copied from the Epic when the conditions are met. If you tried this before and didn't work, let us know

@Alexandra Astor Seems to be a bug in Number fields adopting a default model to display. You can solve this doing the following: Create a custom field 'Short Text' and for this custom field, apply the REGEX function to allow only numbers to create the issue. It works well! About the 'bug' you can see other details…

@Nate Dickinson To import the Request Type you need to go through Jira's global administration interface. Click on the administration gear icon > Click on 'Systems' > Select the option "External System Import" > Select the CSV format > Add the file and map the fields. You can map the Request Type field this way using the…

@Nodar Vardiashvili Is not possible use Password anymore for Web Request on Jira Cloud. This makes part of security policies implemented. You really need to use a token for this. See a bit more here: Deprecation notice - Basic authentication with passwords and cookie-based authentication

@Nate Dickinson , You need to pass the Request Type ID in the CSV and map for Request Type field when you're finishing your import. Also is important map the Issue Type reference of the Request Type. It works fine. Regards, Fernando

@frances.close , In this case, check the board filter. If your board filter only contains: project = XXXX Bringing only data from your project, you will need to adjust this to bring in Epics from other projects. That's because the Epics of these other projects are not fully included on the board, although you can see their…

@Vera Valshonok This happens because your service project uses 'Organization' on the customer section and you're participating one of these Organizations. To see the Organizations, take these steps: Open your project > In the left menu, select 'Customers'. You will see the Organizations created for your project and will…

@frances.close Have you checked 'Filters' in your Plans? Open your Plans > Select 'Filters' > Ensure that the levels are 'Epic' > 'Sub-task'. Maybe your configuration is 'Story' > 'Subtask'. Another thing that could be happening is you are only bringing your project in 'Issues Sources' of Plans. Try bringing the board…

@Tina Leszkiewicz Yes, it's possible. But i'm not sure if will works without an automation rule, but you can try. Your automation rule need to seems like this: Trigger: Scheduled (configure to execute once per month) Action: Create Issue (Select the project, Issue Type and any field you need) - For field summary, select…

@Dhaval Dattani , Welcome to the Atlassian Community! Use this JQL to list issues above your specific Epic: "Epic Link" = EPIC_KEY Example: "Epic Link" = ABC-100 See a litle more about JQL in jira here: JQL: Get started with advanced search in Jira Regards, Fernando

@Kati Samson , Welcome to the Atlassian Community! You can unlink and keep both without any problems. * Go to an issue that contains links and locate the Issue Links section. * Hover over the link you want to delete and click the Delete icon that appears. If you didn't linked the issues using this resource, can you share a…

@Marcos Lopes You are getting this error on some issues because the automation was unable to transition from one status to another. At this point the condition of your REGEX has probably already been checked. The problem is in the ACTION in transiting the issues, try the following exercise: Take an Issue where the…

@Alessandra Cristina da Silva Moraes Duas coisas aqui podem ser a causa do seu problema: 1) O usuário que acessa pelo portal pode estar usando o idioma 'Inglês' como preferência, então ele pode alterar o idioma seguindo os passos daqui: Help customers set their language preferences 2) No recurso do Forms do Jira onde você…

@Marcelo Almeida Como a integração é similar a um modelo de exportação comum, o formato de exibição de campos do Assets realmente será exibindo o object ID. Existe um ticket aberto na Atlassian sobre uma possível correção disso juntamente com um workaround, talvez possa ser útil no seu caso. Consulte mais detalhes…

@Alessandra Cristina da Silva Moraes Você pode sim fazer uma operação matemática em campos do Jira, se você quiser armazenar esse resultado em algum local, o ideal é você ter um terceiro campo para o resultado da operação: CAMPO 1 - CAMPO 2 = CAMPO 3 Na automação do Jira, você deve selecionar para editar o CAMPO 3 e…

@Christian Delgado The log explains that the type of issue you are trying to create is not a 'Sub-task' type and therefore cannot be associated as a 'Child Issue' of your subtask's parent. To be more assertive in your automation, change the ACTION of your automation Instead of Create Issue, use Create Sub-Task Action You…

@Luis Eder Rivera , Welcome to the Atlassian Community! You are using the wrong JQL for this case. The JQL you are using would only work if you were making a condition to read the updated issue itself. Something like: For Current Issue > IF > "Epic Link" = XXXXX As you are using a related issue to fetch the associated…

@Christian Delgado Is there any log that rule presents showing the error? It should be working. But with the automation log we can see other details and help you with the best way.

@Alexandra Astor The message says that the field value does not match the Regex. Apparently you entered one value and the regex function is another. The value entered initially was: 1.23456789E9 At least that's what the Regex had understood. Is there any 'default value' applied to this field? Try other REGEX function with…

@Tony Landowski I don't know if I understood correctly. But if you need to compare several groups you can put them in the same condition or you can also use the same automation rule and compare with IF/ELSE blocks. Hope this helps