Vishal Biyani Expert

Can you confirm you are using cloud? In datacenter all automation rules may not work like cloud. When I tried with {{if(now.format("d").asNumber.lt(10), "First half", "Second half")}} I am getting Second half. if I try with {{if(now.format("d").asNumber.lt(15), "First half", "Second half")}} I am getting first half To…

this will be if condition that you can use {{if(issue.customfield_xxxxx.accountId.equals(issue.assignee.accountId), "MATCH", "NO MATCH")}}

@Gal Fatal In JIRA automation, you can reference the custom user picker filed by {{issue.customfield_xxxxx.accountId}} and compare it to assignee using {{issue.assignee.accountId}}

@Sandesh TM What is the business use case for doing this? One approach that I can think of is, have a specific workflow for the issuetype that you don't want to allow users to create issues for. In the create transition, add a Validator with condition that can't be met. That way if user tries to create the issue with the…

@Ali Ahmed Dar Your problem statement is not clear. if you want to have a logic for 1st half of the month or 2nd half, this is how if works {{if(now.format("d").asNumber.lt(15), "First half", "Second half")}}

looks like you are using External System Import. Assuming your project exists, can you go to Filters -> View all issues Then click on ... and select import issues from csv. Can you try from here and see if it works for you?

@Saravanan Prabhakaran if you are creating new issues, why are you including "Issue ID" in your csv import file? Have you tried by removing this column and see if import works? Is there any specific business reason for having blank Issue ID column in csv?

No harm in trying it out. However, issue. will give you access to values for triggerIssue value not the lookupIssues.

@vaibhav bisht Exploring further as per this documentation link, the lookupIssues in data center may be supporting limited fields. That could be the reason why you are getting an empty value for lookupIssues.customfield_10800 in DC while it works in Cloud. Jira smart values - issues | Automation for Jira Cloud and Data…

customfield_10800 field looks correct with name = Company. As you are using jql: assignee = {{issue.assignee}} and company is not Empty if it returns more than 100 rows, it may not work as lookupIssues has a limit of 100. Add the log message for {{lookupIssues.customfield_10800}} it should show the values. for the counts…

Can you hit this url and show what value is coming for the custom field corresponding to Company field? This will also confirm that customfield_10800 maps to Company https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names yourinstanceurl would be your datacenter url and <issuekey> should be replaced with your…

@vaibhav bisht After your call to lookup, can you add a log statement, to see what values you are getting in the field. {{#lookupIssues}} {{customfield_10800}} {{/}}

@vaibhav bisht Below article mentions the JIRA Datacenter versions on which automation works We're bringing the Lookup Issues and Create Variable actions to Automation for Jira Data Center What is the version of jira data center that you have?

@Gowri Kumar For this automation to execute, there are two requirements that need to be met. First the scope of the automation needs to be multiple project. The scope can be modified in Global administration. Second You will need to ensure that fixVersions that are available in Project 1 (Epics) are also available in…

based on the SS, it could be ADM-36

Glad to know this worked for you

That URL shouldn't give error. Can you recheck? Also, the issue is not with Target Start Date. The issue is how fixVersions is being accessed. As you are using a custom field, Target Fix Version, it is important to see the o/p from above URL. How can you confirm the Target Fix Version only accepts 1 value? if it accepts…

@Anna Shpilkovsky if you remove the quick filter, what happens? I suspect the backlog filter is querying for issuetype = story and hence you are not seeing other issues when this filter is selected.

@Ramesh Krishnan As far as I know, the team field is not available in the gadgets. The work around is to create a custom field and use JIRA automation to populate this field when Team field is updated. Then use the custom field in the gadgets say two dimensional filter

@Roberto Carvalho This message only applies to the gadgets that you are using in your dashboard. There is no impact to your JIRA instance due to few gadgets being removed.

@Alice Mason Most likely the issue is how you are accessing the field value. Is TargetFixVersion a custom field in your jira instance? Are you sure it has startDate? Can you check the available values by using the URL and share what you see for TargetFixVersion?…

@Ari Raatikainen This will give the correct sum product. {{#=}} {{#lookupIssues}} {{valueY}} * {{valueX.asNumber}} {{^last}}+ {{/}} {{/}} {{/}}

@Ari Raatikainen if I understand it correct, you want to do sumproduct. Below works., {{#=}} {{#lookupIssues}} {{valueY.multiply(valueX.asNumber)}} {{^last}}+ {{/}} {{/}} {{/}} Can you check and see if this works for you?

@K Rahul Why do you think the original estimate will change? The Remaining effort should show 2 hours.

Catching up on emails is an activity that helps utilize the time

@Aleena Umaiir lookupIssues can be looped through to get sum of values. Could you share the rules/calculations that you have put so far and what issue you are facing? that will give better understanding of the issue you may be facing.

@Jonny FixVersion and Affects Versions are a list field. You can start by creating a variable and create a json string of matching fixVersions like this {{#lookupIssues.fixVersions}} {"name": "{{name}}"}, {{/}} Then when you edit the fixVersion use something like { "fields": { "versions": […

Good to know that you are able to make progress. JIRA Automation has a limitation that you can't have nested branches. Therefore, the way I put the logic together was in the smart variable varFilteredFixVersions create pairs of name and fixVersion as a json string like {"name": "ABC 123"}, {"name": "ABC 456"},…

@RRACHAKO Go To Dashboard -> View All Dashboard. You will see More action -> ... Click on ... You will see Rename or share dashboard There you can give editors permission or viewer permission

@Ernst Rudolf Lübkert Can you try clicking on Home -> Add-ins. Then Go To My Add-ins. On the right side you will see Manage My Add-ins. Click it, it will take you to office 365. There try to hide it and see if it helps remove the add in.