Fernando Eugênio da Silva Community Champion

@Michael Wolfe Have you tried adding an ELSE negating the entire IF condition? So the behavior would be: if the IF is not true, assume normal behavior. else { subCategory.setRequired(false) subCategory.setHidden(false) subCategory.setReadOnly(false) categoryRF.setRequired(false) categoryRF.setHidden(false)…

@Darrian Castillo Just use the AND incrementing feature in your JQL, so it would look something like this: due date> = start OF day() and due date <=end of day() AND status != Done This should already work for you. As a suggestion, I would change the "status != Done" to "statusCategory != Done". Only if it's the case you…

@Peter Strömberg , welcome! The ability to view issues through the customer portal as per the screen you showed is only available to Jira Service Desk users accessing the issue. In addition to the reporter, others can only see this request through the customer portal if they meet one of the following requirements: 1) It is…

@Thiago Hartmann , Another solution that I ended up developing here very quickly and practically and that certainly works is to use the JSON language to update the Component adding the value you want. See the payload below: { "update": { "components": [ { "add": { "name": "AV" } } ] } } For that you don't need to put the…

@Thiago Hartmann The "ADD existing values" feature to components is only available using "Copy from". The only possible way for you to do this is as follows: Add a new ACTION of yours where you select the "AV" component In this new ACTION, select the EDIT issue for the "Component" field and this time make the formula for…

@Thiago Hartmann Can you share the full details of your Cloud automation? I did some tests here and I can confirm that Cloud has the "Copy value from issue" option, but I didn't want to give you an answer that might not be so helpful. If you can share how your automation is formed, maybe I can help you fix it and get the…

@Boswell, Richard , I can do this using the following payload in my JSON "customfield_XXXXX": [ { "workspaceId": "WORKSPACE_ID", "id": "WORKSPACE_ID:OBJECT_ID(NUMBER)", "objectId": "OBJECT_ID" } ] How to get WorkSpaceID: Access the URL: https://URL/rest/servicedeskapi/insight/workspace; Collect the ID present in…

Hahaha, now you know, man! Good job!

@Tony Hernandez Hey Tony! It is possible, but you will have to use advanced JQL features for this. See how to do it: In the second pass condition, change the condition to "JQL CONDITION" and try something along these lines: "Manager 1[User Picker (single user)]" in membersOf("site-admins") That is, I'm saying that the user…

Hey Tony! Great! That way I believe it won't be difficult for you to set up this automation. In automation for approver 2 use the trigger: Issue Transitioned: FROM > Waiting for Approval TO: Wiating for funding approval; Follow the same idea of the conditions that are in the print and test If you have difficulties, let us…

@Natália Roman , O status Backlog é o primeiro status do seu fluxo, antes disso não é possível adicionar comentários na issue. Eu acredito que você deva fazer o seguinte primeiro: Crie uma pós função que adiciona um comentário com este conteúdo; Depois faça a ordenação para a seguinte: 4: Pós função que adiciona comentário…

@Felicia Rodrigues Note that in addition to the mandatory errors, some other fields also present an error of not being present in the screen layout. I know this is something that we can easily solve, send us a new print of the audit log of the new tests done. Before, ensure that all the fields you are taking in your…

Do these approval stages take place in the same status or is Approver 1 in one status and the second approval is in another status within the same flow? This will help you better understand how to build a basic automation rule. Thinking about the scenario that each approval is in a different status, you can put together…

@Suresh Srini The easiest way to find out why is to use the permission helper. The Permission Helper is a feature that assists with quick troubleshooting of permissions in Jira, so if you are unable to perform this action on this particular issue I would recommend you try this first. It could be some "Issue Security"…

@William Yesid Sanchez Perez A simple case that can help is you increment the filter you are using your backlog/board with the following JQL: AND status != Canceled If that's not enough, come back with more details and some screenshots for us to evaluate. Regards, Fernando

@Felicia Rodrigues As these fields are mandatory you will need to enter a value for them. Unfortunately automation doesn't have the ultimate power to skip validations and field requirements. So the only ways you can achieve this are: 1: Inside the ACTION of "Create Issue", add the mandatory fields and you can choose some…

@Felicia Rodrigues Change the BRANCH to the option "For Most Recently created issue". This BRANCH type will only collect issues that were created in this automation event rule. Since you separated the events by condition, it should read only the creation event for each condition included. If that doesn't help, come back…

@Ingo Strohmeyer , you´re welcome! You can add user email addresses that exist in your Atlassian environment. For example: If this is a Jira Service Management project, you can use a customer (unlicensed) user or you can use licensed users as well. If you want to use the auto-assign by groups feature, then only licensed…

The best way to export issues to Excel is using the detail view visibility. After assembling the JQL in Jira to extract data, select the following option: After that, click on "Colummns" and place the fields you want to export to Excel. Everything you mark will come in column form in your excel. If you want the ticket ID…

@Dru Hoagland No, this is not possible. What you can do is create a screen between the 2 status transition. Add different custom fields on this screen where you consume the values of Summary, description, etc. Configure automation with the trigger: Issue transitioned > ACTION > Create issue In summary, click on the 3 dots…

@Natália Roman , Entendi! Obrigado por compartilhar mais informações. Usando recursos nativos de JQL do Jira eu acredito que você não consiga extrair essa informação sem relacionar a uma issue em específico. Você consegue extrair esses resultados usando o app Script Runner em sua pesquisa avançada de "Enhanced Search".…

@Ingo Strohmeyer Here's the best way you can do that. In the Schedule, include any issue from the project you are configuring this automation for. We'll need it to be able to randomly assign the assignee next. See an example: Then configure the issue creation with only the summary and the project details and issuetype, see…

@Natália Roman , Eu tentei o mesmo recurso de JQL que você mostrou e para mim parece funcionar bem, veja: Peguei a issue: SS-79; Adicionei 2 issues com linked issues diferentes Em seguida, apliquei a JQL: issue in linkedIssues("SS-79") no Jira e ele me trouxe os resultados das duas issues relacionadas: Para garantir,…

@Ingo Strohmeyer The error is occurring because the ACTION of Assignee issue is outside the scope of Create Issue. You need inside the ACTION to create issue, include the "Assignee" field and select the assignee assignment options. By your logic, Jira should change the Assignee of something in the Schedule, but you don't…

@Bill Sheboy If you use this Due Date <= EndOfMonth() scenario Jira will raise questions that the Due Date field value is less than or equal to the end of your current month. Then, each month will be renewed automatically by the Jira filter. Let me know if this helps you. You can also see more details on the Atlassian…

@Kelli Keith This counts the full month referenced. If the action happened within that month and Jira recorded it, this should count normally

Hey, @Kelli Keith ! Yes, it´s possible. For that you need to use the following JQL to be something that changes automatically month after month. JQL: updated >= startOfMonth(-1) AND updated <= endOfMonth(-1) This JQL is automatically filtering out issues that were updated from the beginning of last month to the end of this…

@sujit kumar You can create these automations within the project. As each version is something individual in the project, you can do this in the "Automation" feature in the project settings. I believe they are available for Standard yes. I do not recommend using the Global Automation feature because depending on the number…

@Юманкин Д_М_ You are unable to find fields of type "Select List (Cascading)" in Jira Cloud due to automation. To indicate some value for it, you will need to make use of the smartvalue feature, expanding the "More options" option and using JSON to reference the values of the Select List Cascading field Luckily I have a…

You can use this simple automation concept and refine it according to your needs: The automation logic is as follows: > When a version is "Released"; > Read issues within the release; > Transit issues within the "Released" version to closed I hope this helps. If you need any question, let me know. Regards, Fernando