Alexey Matveev Expert

Try like this and put the post function last in the list of post functions. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.event.type.EventDispatchOption import com.atlassian.jira.issue.CustomFieldManager import com.atlassian.jira.issue.UpdateIssueRequest import java.text.SimpleDateFormat…

Make sure that you put user:userpassword correctly to base64. 

It means that you are not authorised to Confluence. Try to authorize like in the article, which I provided.

Try not to login to confluence in your browser and execute the rest. Have a look at the returned value.

You put your script in the Condition part, but you need to put your script into the Additional Issue Actions part

I guess, so. The problem is with cert

If you execute by curl then it must be like this curl -D- \ -X GET \ -H "Authorization: Basic dXNlcjp1c2Vy" \ -H "Content-Type: application/json" \ "https://your-domain.atlassian.net/rest/api/2/issue/QA-31" The Authorization part you do like this: * Supply an Authorization header with content Basic followed by the encoded…

Kindly make sure that the Rest Api Browser installed and enabled

Kindly have a look at the KB below: https://developer.atlassian.com/cloud/confluence/basic-auth-for-rest-apis/ It is written there how to provide values for basic authenticaion.

You can use the library, which I gave you. This library is for querying Rest Services. It does not matter, if the services are in Jira or not.

I do not think it could be a problem. But try to fix it.

Do you try Postman on the Jira instance pc? I mean you should try it on the same pc, where Jira is installed.

Try to change your script to this one import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.event.type.EventDispatchOption def user = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'MyCustomFieldType'}…

What do you mean it is not working. Try to log to the log file the value of getIssueType().getName() log.error(issue.getIssueType().getName() ) and see its value.

You would need to develop your own JQL functions, either by Power Scripts or ScriptRunner plugins

How would you know if sub task exists or not?

The problem is that issue is not connected to a board. It is the board, which connects the issue by a JQL filter. You can user Jira Software Api to iterate over all boards and then get issues for each board and search for the required issue GET /rest/agile/1.0/board GET /rest/agile/1.0/board/{boardId}/issue

You code works fine. Make sure you enter the right user and the user password. And you use basic authentication in your Jira instance.

You would need to create your own custom event. Then fire the event on a transaction. You should add the event to the notification scheme and change the vm file for the event. https://confluence.atlassian.com/adminjiraserver071/adding-a-custom-event-802592793.html…

You should try Jira plugin tutorials first and you should understand, what modules you can create in Jira. There is no such module as call an external service. Did you develop any program before (not a Jira plugin)? How would you call an external service from there? You would do the same way in a Jira plugin. Module are…

If you want to use a groovy script, then you need a plugin. Out of the box you can not execute groovy scripts.

You should learn how to search the Jira Java Api. If you find the Issue class, then you will see, that issue.getIssueType returns IssueType object and that is why you are completly right you have to use it.getIssueType().getName() If you are not sure about any value in your script, you can use log.error(variableName) 

Do you mean, that there is no NullPointerException anymore? If so, then where did you attach the post function? Is it the create transition? Is it last of first in the list of postfunctions?

It is not Jira, which is responsible for handling transactions during backups. It it pg_dump. It is written, that the backup will be consistent. You can try to look for confirmation in the oficial documentation or ask on the relating forums.

ScriptRunner and Power Custom Fields are plugins. You should find them in System->addons

If you have Power Custom Fields or ScriptRunner, you could create a custom field, which would show you the number of times the issue was reopened.

I guess, you are on Cloud. Did you use the update issue field post function? If so, I am not sure how you got ther -1 value. I think you should remove the Resolution of the issue will be set to -1 post function and publish the workflow.

You are asking from the user point of view? Not as an administrator? In clould the url has .atlassian.net suffix. I do not know how to distinguish data center from not data center, if you do not have Jira admin global permission.

You need to define where you want to call the Rest Service and create this module. Maybe, you call it from a post function or validator. But anyway it is better to make your rest call service as a service in Jira (Named annotation)

Issue_Updated event does not fire, when status changes. You need to add Trigger a Webhook post function to the required transactions.