Alexey Matveev Expert

There are three screens, which you can define for an issue: create, edit and view. If you have a filed only on the view screen and the field is not present on the edit screen, then you will not be able to edit the field. What do you mean by nothing changes? You can still edit the field, can not you? If so, check that the…

I am not sure, how you call the script. But it seems to me that there is a error. You call getCustomFieldValue, but you should call issue.getCustomFieldValue.

You have to make sure that the group is not included for the browse issues permision for the required project.

Try with AJS.$.post()

com.atlassian.jira.issue.field.UserField

You should write like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue def issue = ComponentAccessor.getIssueManager().getIssueObject("MAV-2") def changeHistoryManager = ComponentAccessor.getChangeHistoryManager() def createDate = issue.getCreated().getTime(); def…

I think, you need a plugin for it. For example, ScriptRunner or Power Scripts.

90% of sciripts begins with the ComponentAccessor class. You can find API about the class here: https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/component/ComponentAccessor.html You need to import the class first in your script: import com.atlassian.jira.component.ComponentAccessor Then you need…

That would be defined by an inherited interface of the custom field class. If it is not your plugin, then you can not influence it.

I tried your script like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.ModifiedValue import com.atlassian.jira.issue.util.DefaultIssueChangeHolder def customFieldManager = ComponentAccessor.getCustomFieldManager() def issueManager = ComponentAccessor.getIssueManager() def…

The script should be like this: import groovyx.net.http.HTTPBuilder import net.sf.json.JSONArray import org.apache.http.HttpRequest; import org.apache.http.protocol.HttpContext; import org.apache.http.HttpRequestInterceptor; def JIRA_API_URL = "https://yourjiradomain" def jira = new HTTPBuilder(JIRA_API_URL);…

Try like this: import groovyx.net.http.HTTPBuilder import net.sf.json.JSONArray import org.apache.http.HttpRequest; import org.apache.http.protocol.HttpContext; import org.apache.http.HttpRequestInterceptor; def JIRA_API_URL = "https://jira-test.raiffeisen.ru" def jira = new HTTPBuilder(JIRA_API_URL);…

Kindly change your script to this one and have a look at the logs. Either epicIssue or epicLink are null and that 's why update does not work. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.ModifiedValue import com.atlassian.jira.issue.util.DefaultIssueChangeHolder def…

What was the error?

what does it mean fields=""? Try to skip it. make your url like this /rest/api/2/issue/SD-233373?expand=changelog

Then you need a plugin: Power Scripts, ScriptRunner, JQL Tricks

You can use the Select List (Cascading) custom field.

Then it worked fine for me

You should go to the project settings. Then choose the Workflows menu option. Find workflows for the issues, for which you want to change the Resolution field. Edit the workflow and add a transition from any status to itself. Then add the Update issue field post function, where you set the Resolution field to the required…

You can choose all NOT subtask with issuetype in standardIssueTypes() This function is out of the box.

You can create a transition for the required issues with a post function, which changes the Resolution. Then you can execute the bulk edit operation, choose the Transition issues operation and execute the created transition. Or you can use a plugin like Scrptrunner or Power Scripts. ScriptRunner has a built in function…

Kindly read the following guide: https://confluence.atlassian.com/adminjiraserver071/backing-up-data-802592964.html

If 10905 is the option id then your json should be like this { "serviceDeskId":"1", "requestFieldValues":{ "summary":"Test", "description":"Testing", "customfield_11802":{ "id": "10905" } }, "requestTypeId":"59" }

Unfortunately, you can not do it with Service Desk automation.

You should create a different screen for the edit view screen and remove the required field from the screen and attach the screen to the screen scheme in the project. I attached a screenshot: Kindly read the articles below: https://confluence.atlassian.com/adminjiraserver/defining-a-screen-938847288.html…

I tired this one curl -D- -u username:password -X GET -H "Content-Type: application/json" https://jiratest:8443/rest/api/2/issue/SD-23337 it worked just fine. You have a Jira Server right? not Cloud?

That would be a better option. But sometimes Jira must be up 24/7 and it is not possible.

What is in the Codition field right now?

That is a very strange behaviour. Could you provide your source code? Or better take the source code from Bitbucket and try it: https://bitbucket.org/serverecosystem/message/src/b4036f4a4fd68020a281ee6a3109cb398a8aa0da?at=master

Are you sure that the post function is executed?