Tom _Automation Consultants_ Atlassian Partner

@Emilee Thanks for letting me know!

Thanks for this great article! It's always nice to see what new apps have been released, and how they might help improve our Cloud Instances. We also released Workflows for Confluence this quarter and wanted to know how we could get added? 

I understand that it's a huge security flaw and I believe Atlassian are trying to address it. I'm not 100% sure about this behaviour but I would say that it's either: * How Atlassian have designed their API so there's no workaround * Due to you searching for Issues, Jira needs to know your credentials to verify if you…

You need to add a header that authorises your request: https://developer.atlassian.com/server/jira/platform/basic-authentication/ Look under the "Construct the authorisation header" section.

Apologies that was for a Standard select list not cascading. I have made some changes to your code, please select the field 'reqtype' in the Behaviours section, and add this server side script: import com.atlassian.jira.issue.Issue; import com.atlassian.jira.issue.fields.CustomField; import…

If you visit the {Jira Base URL}/secure/admin/ViewLinkTypes!default.jspa And click on the Blocks edit button in the URL will have the ID of the Blocks IssueLink (mine was 10000) Then in the Scripted Validator add the following code to a Simple scripted validator (in the condition section): import…

Hi Krithica, Here is a snippet of the code that I have used previously with Behaviours: "ValueA",<span> </span>"ValueB"]<br>def cf1 = getFieldByName("CustomField_A")<br> def customField = getCustomFieldManager().getCustomFieldObjectByName("CustomField_A")<br>OptionsManager optionsManager =…

issuetype NOT IN (Sub-task) or if you have ScriptRunner App installed, you can use (this will apply the filter on all Sub-task issue types): issuetype not in (subTaskIssueTypes())

import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.issue.IssueFactory import com.atlassian.jira.exception.CreateException def newIssue = ComponentAccessor.getIssueFactory().getIssue() newIssue.setProjectId(15530L) newIssue.setIssueTypeId("6")…

I would in this case create a new Mutable Issue instead, set all the values you're current setting using the issue input parameters. Set the custom field value but pass it the option instead of the string (issue.setCustomFieldValue(field, option)). Then use the Issue Manager class to call the create issue function with…

No worries, there is an answer here https://community.atlassian.com/t5/Jira-questions/Read-only-field-only-in-view-screen/qaq-p/982404 tl;dr This needs to be in the behaviours initialiser: def customField = getFieldById("custom_field")customField.setAllowInlineEdit(false)

Remove the field from the edit screen if they're read only. That way you don't need to use behaviours to make them read only.

Hi @David Antebi , Maybe try passing the Option itself not the .toString() of the Option?

Can you write out to the logs the value of the selectedOption? It might be returning null which is why it isn't being set. Also you're calling it.value == selectedValues[i].toString(), you could try it.value.equals(selectedValues[i].toString()). You could also try putting the strings down to lowercase just in case the…

if(iLink == null){ continue; } can you add this bit of code just beneath the for(IssueLink iLink : linkedIssues){ part of the code. 

@Aisha M If you go to the Scripted Fields part of ScriptRunner in the Add-ons settings there will be outputs to the logs, could you attach a picture of the most recent log? Also on the Program Epic issue can you in the Admin section select the Where is my field? button and search for the scripted fields name and attach…

@Aisha M No problem! Yes it will get the inward links of the Program Epic (as long as you put it on the screen for that issue type) which will be various Epics. From there it'll loop over the linked issues (there is no checking that they're of a specific issue type, you can add this in if there will be other issue types…

import com.atlassian.jira.issue.link.IssueLink; import com.atlassian.jira.component.ComponentAccessor import java.sql.Timestamp def issueManager = ComponentAccessor.getIssueManager() def customFieldManager = ComponentAccessor.getCustomFieldManager() def dueDateField = customFieldManager.getCustomFieldObjectByName("Due…

import com.atlassian.jira.component.ComponentAccessor import java.sql.Timestamp import java.time.DayOfWeek import java.text.SimpleDateFormat; def plannedStartDate=ComponentAccessor.customFieldManager.getCustomFieldObject("customfield_16160") def otherDate =…

I'm currently replicating the problem in my local instance, will get back to you shortly

ComponentAccessor.customFieldManager.getCustomFieldObject("customfield_16160") needs to become ComponentAccessor.getCustomFieldManager().getCustomFieldObject("customfield_16160")