Fernando Eugênio da Silva Community Champion

@Angela , Welcome to the Atlassian Community! Are you using project Team-Managed or Company-Managed? Because , if you´re using Company-Managed project, the step by step published on link that you shared it´s functional still. Go to Project Settings > Go to Workflows > Click on "Add workflow" > Look for your workflow and…

@Aditiya Panday Naturally, this is not possible. I believe it is possible using the Jira Misc Workflow Extensions app and applying a field required validator (JMWE) or using the built-in your script validator. You can use the JMWE trial period to test this solution.

Mario, In fact, if the field is of type number field, leaving the value empty or null will cause automation errors or the final result to appear incorrect. Instead, try to instruct your users to use the number 0 or 1 and not leave the number field empty. I think this will be enough to help you. If this doesn't work or it's…

@RAJKUMAR DURAIPANDIAN Doesn´t this works for you? creator = currentUser() If don´t bring the correct results, please, share more details about what you want extract

@Karen Corbeill The automation log indicates that the automation stopped at one of the imposed IF conditions. I would recommend that you review that all automation conditions equally meet the Team Managed project as well as the Company Managed. If you still experience issues, please share the automation framework here so…

@Ben Newton , hey, that´s simple. To increase the number of issues using this Confluence feature, do the following: Click on the "Display Options" option after selecting the query and doing the search: Then set the maximum number of issues that should be displayed in this option here: Hope this help you. BR, Fernando

@Laurien Scoville In order for reopened tickets to reappear in your "All open" queue, you must edit the queue's JQL query. When accessing the queue, click on the 3 points located on the right part of the screen and then select the "Edit Queue" option. Adjust the JQL query to look for also reopened items and then save, by…

Hey, @Alexey You need to use project role: "atlassian-addons-projects". Users like automation or other users created by third apps are includ in project role "atlassian-addons-projects" not a group in jira. Hope this helps. Best, Fernando

Hey, @Steven Lees-Smith . You can use the smartvalue: {{issue.customfield_XXXX.displayName}} Then the Jira will show the complet name from the user present in the customfield. See de guideline: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ Best, Fernando

hahahaha The error can happen as follows: You don't have a transition that goes from the "Pending External Information" status to the "Awaiting User Confirmation" status, so when your automation is executed, Jira will not be able to move the issues because those that are in "Pending External Information" will not will…

@Jessie Daniel Manansala Can you see if all the flows of the issuetypes of the "Support" project have transitions released for the status "Awaiting user confirmation"? The error you receive indicates that Jira was unable to identify a path (transition) going from some statuses to the "Awaiting User Confirmation" status. A…

Hey, @[deleted] ! I think this can be help you { "update": { "CUSTOM_FIELD_NAME": [ { "set": { "value": "{{triggerIssue.fields.CUSTOM_FIELD_NAME.value}}", "child": { "value": "{{triggerIssue.fields.CUSTOM_FIELD_NAME.child.value}}" } } } ] } } Other informations you can see…

@John Bacon To drag the subtask to the 'Complete' column, you need to ensure that there is some subtask flow status associated with the 'Complete' column. Especially in Sprint cases, it is recommended that "Done", "Closed", "Canceled" status be mapped within the "Done" column of the board, because this will make Jira…

@Khyati Pitroda I see this video. This is a behavior that really deviates from the expected. I believe that in this case, it would be more interesting for you to try a direct solution with Atlassian support, through the link: https://support.atlassian.com/contact/ Please try opening a support ticket directly with Atlassian…

@Krishna Raghavarapu Take a look: { "update": { "CUSTOM_FIELD_NAME": [ { "set": { "value": "{{triggerIssue.fields.CUSTOM_FIELD_NAME.value}}", "child": { "value": "{{triggerIssue.fields.CUSTOM_FIELD_NAME.child.value}}" } } } ] } } This works for me It is important to remember that the cascade field must be available on the…

Bem vinda à comunidade Atlassian, @Erica Alves . Para associar uma tela entre as transições, você deve fazer o seguinte: Crie uma tela no Jira e adicione os campos que você quer fazer aparecer nesta transição. Em seguida, vá nas configurações do projeto e clique em "Workflows"; Clique para Editar o Workflow da Issuetype…

@Rosa Osorio Arteta , Puede extraer el filtro, pero no se actualizará automáticamente, deberá "actualizar" Excel cuando desee ver la base de datos actualizada. Haz lo siguiente: En el filtro que ha guardado, haga clic en la pestaña para conectar JIRA a excel directamente a través de este icono: Luego, dé permiso para que…

Ricardo, Você só pode associar mais de um fluxo ao projeto se for associá-lo à issuetypes diferentes. Se a ideia é associar dois fluxos de trabalho à uma mesma issuetype, isso não é possível. Se você já tiver uma issuetype no projeto que vai receber este novo fluxo, para associar o fluxo à esta issuetype, siga este…

Albert, Please, try this: { "update": { "summary": [{ "set": "{{triggerIssue.customfield_10951}} + This is my text" }] } } I tried this and it worked as expected. However, to do this you have to indicate the summary value only by JSON and not load it as a field in the creation. You need to indicate it here only: Let me…

@Khyati Pitroda , welcome to the Atlassian Community If you are using a Team Managed project, this could be because the status the ticket is in has not been included on the board. Try the following: Access the board; Click on "Configure board"; Map your flow statuses to board columns by dragging them. From there, whenever…

Ricardo, Se o cliente está na organização, o campo irá aparecer na tela de criação do portal: Então o usuário deverá selecionar se quer compartilhar com a organização ou se quer abrir a solicitação privada, onde somente ele terá acesso. São requisitos disso estar cadastrado dentro da Organization do projeto. Talvez o modo…

@ketty_silva , Aparentemente você clicou em algum filtro do Trello e por isso os cards foram colapsados. Verifique se no canto direito da sua tela, em "Filters" se há filtros aplicados. Se sim, basta clicar no X e os cards devem voltar a aparecer na tela. Veja o print: Se isto não resolver, nos avise :)

@it-arief.heldian Yes, this is possible. But this is a project-level configuration. In projects where these people from external domains cannot open tickets through the customer portal, the permissions of customers must be changed. Go to "Project Settings"; Click on "Customer permissions" Make sure the "Service Project…

@Matt Sardi A suggestion that might work for you is to do the following: Add an auto transition to your flow. Click on the issuetype workflow; Click "Add transition"; Select "From: Any status" > "To: Itself" options. Give her a name. Add a screen to this auto transition and include the "Approver" field on it. Publish these…

Ricardo, Aqui estão alguns passos que podem ajudar a identificar a causa: Verifique se o cliente em questão está devidamente adicionado à organização; Verifique com o cliente se ao criar o ticket no portal, o campo "Organization" aparece ao final da tela e se o mesmo não está indicando "Private Request" ou está preenchendo…

@Matt Sardi You can easily change this on the Jira screen itself. Do the following: Click on "Project Settings"; Go to "Screens"; Go to the issuetype and screen layout you want to change. In the "Edit and view" screens, add the "Approvers" field. Then go back to the issue in Jira and change the approver to the user you…

Albert, About the error you are seeing, can you confirm if the ID field 10951 is a custom field of type select list or checbox? This changes the JSON structure a bit. As for updating the summary also when the field is edited, I would recommend the following: Create a new automation with the following details: Normally…

@Fellipe Demoraes , welcome to the Atlassian Community. This error indicates that the field "Country - SMFC" is mandatory to be filled in when creating your issue. So you must indicate some value in it to move forward in creation. You can remove this requirement by reviewing these two options: Click Project Settings: Go to…

@Albert Manuel Maybe you can do this: Create the initial scope of your automation and after the condition of "Issuetype" = Epic Add a BRANCH; Use the option "Branch rule / related issues"; Select the "Stories (or other issues in Epic)" option After that, inside the BRANCH add the "Edit Issue" action and place the JSON…

@Marcela Rojas In order for these fields to appear to include them in the Request Type, they must be present in the issuetype creation screen where you are associating this Request Type. Can you confirm that this is configured this way?