Alexey Matveev Expert

Ah, I see. I would avoid this solution. It is not simple to move issues between projects programmatically. Maybe you can use components instead of projects? You can read about components here: https://confluence.atlassian.com/jirasoftwarecloud/organizing-work-with-components-764478279.html

It works correctly. In the script you look for subtasks, that is why your script works only for the parent task. Your scripts for the create subtask and update parent task must be different. For the create event you should get the parent of the issue, get the fix version and save it to the event issue.

I thought you wanted to hide certain request types for certain groups in the Portal. It can not be done in the Portal. But you can change the value of the request type field to the one you need, depending on the user group, in a post function. I think you can do it with ScriptRunner.

You can hide the move button with the Hide UI element built in function in ScriptRunner. You can set a condition that the button will be visible only for certain issue types. https://scriptrunner.adaptavist.com/latest/jira/fragments/HideUIElement.html

Hello, You should check the Browse Issues permission for the project which must not be seen by users. You should remove the users from any group or role which is set there. You can read more about permissions here: https://confluence.atlassian.com/adminjiraserver073/managing-project-permissions-861253293.html

Service Desk Agents receive notifications for internal comments.

It is not possible. Here is the ticket: https://jira.atlassian.com/browse/JSDSERVER-195

As far as I understand, you want to limit issue types based on user groups. It is not possible.

Hello, You can use this class https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/sal/jira/scheduling/JiraPluginScheduler.html Here is an example https://bitbucket.org/cfuller/atlassian-scheduler-jira-example/src/master/

Try to execute it.

What is exactly the error? Maybe you passed wrong parameters to the method?

Jira Service Desk already contains shared and internal comments. Why do you need a custom field?

You should write like this: if(getAction() !=null) { //your code here } You can find more info on getAction method here: https://scriptrunner.adaptavist.com/latest/jira/behaviours-api-quickref.html#_getaction

Change IssueManager issueManager = ComponentManager.getInstance().getIssueManager(); to IssueManager issueManager = ComponentAccessor.getIssueManager(); and import com.atlassian.jira.component.ComponentAccessor

I think you added this post function on issue creation. You should put this post function last in the list of post function. Right now I guess it works before the issue is saved to Jira.

If it is a RESTful service, then you can read the following thread: https://community.atlassian.com/t5/Answers-Developer-Questions/Making-a-REST-call-using-script-runner/qaq-p/576712

Hello, What is your project type? Is it a software project? To ask it another way. Is it a business board or Jira software board?

Hello, You can check it yourself. Try to add : log.error("requestParticipantList class: " + requestParticipantList.getClass()) to the end of your script and have a look at the output in the atlassian-jira.log file.

Hello, First you need to understand why your resolution is not set when you move to the Resolved status. Have a look at the transition to the Resolved status and there must be a screen with the resolution field or you must add the Update Issue Field post function to set the Resolution field automatically. If you want to…

The java home environment variable must be called JAVA_HOME. In your case it is java.home. You can find more info here: https://confluence.atlassian.com/crowd/setting-java_home-61604243.html

Hello, You can develop your own Jira plugin the integrate Jira with another system or you can use the built-in functionality, called Webhooks. Webhooks are REST calls, which are executed on Jira events or post functions. It is a REST call to an external API. You can read more about webhooks here:…

Hello, Go to my.atlassian.com and generate a new trial license.

Hello, Look at the jiraissue, changegroup and changeitem tables.

Hello, I also have the same warning message in my Atlassian-jira.log file, but I still can login. I suspect that you put the wrong username or password. You can try to retrieve the admin password by following this guide: https://confluence.atlassian.com/jira/retrieving-the-jira-administrator-192836.html

You can not do it out of the box. You would need an add-on like Power Scripts, ScriptRunner, Automation for Jira, Workflow Toolbox.

@Tarun Sapra It is a good article. Thanks a lot!

Hello, Technically there is no difference between "contains in" and "relates to" links. They are just links. They do not contain any code behind them. Links are for users to understand business purpose of the link. Out of the box only subtasks can be summed up to the parent task. 

You can find an example of such a script in this thread: https://community.atlassian.com/t5/Jira-questions/Automatically-add-request-participants-on-SD-ticket-creation/qaq-p/89008

I do not know how to remove this tab from the view issue screen. But it is important information. It shows you how the ticket was created and what the request type is. If the Request type field is empty, then the ticket is not visible in the portal.

Hello, Are you on Cloud or Server? If on Cloud then you can not do it. If on Server you should use such add-ons like Power Scripts or ScriptRunner. In ScriptRunner this functionality is called behaviours. In Power Scripts it is called Live Fields.