Alexey Matveev Expert

Kindly push the Edit button in the screenshot below:

You need a plugin. The scripts, which I provided, can be run by ScriptRunner. You can also use Power Scripts add-on. But there will be a different script. The script will be easier.

Which fields must be on the screen? If there is a duedate or assignee, then you need schedule issues and assign issues permissions. I you do not have them and these fields are the only ones on the screen then your screen will be empty.

You can use Jira Rest Api with changelog paramter. You can find more info here: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-issue-issueIdOrKey-get

Yes. You can write a condition for which project and issue types to hide

You can hide the button using ScriptRunner web fragments: Hide system or plugin UI element

A project does not have any status, that is why you can not check it. Or give more details on what you are trying to do.

Do you want to populate a group of an assignee to a group picker? And what if an assignee belongs to multiple groups? That is how you populate a group picker import com.atlassian.jira.component.ComponentAccessordef customFieldManager = ComponentAccessor.getCustomFieldManager()def groupManager =…

Hava a look at the Application-> Application Access. What is the default user group for the Service Desk Applicaton? Add there a group from AD to which all users belong.

There is a problem with a listener. You should correct the Null Pointer Exception. As far as I understand your version is created correctly, is not it? And you can choose later manually for another field? Try to just to create a version with your script and see the result. Then you should corrent your Null Pointer…

You can not copy assignee value to a group picker, because assignee is of the ApplicationUser type and group picker is of the Group type.

I am not sure, why you have such behaviour. I think you should check log files

I just tried your script. It works fine for me. Your script creates a released version and then I can choose the version for an issue without additional actions.

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 SimpleDateFormat monthFormatter = new SimpleDateFormat("MMMM");…

What is your Jira version?

If you mean, that you can not see the field on the view screen, then you can see a custom field on a view screen, only if the field has a value, otherwise it will be hidden. Try to use the Where is my field functionality.

You can use Jira Software Rest API https://developer.atlassian.com/cloud/jira/software/rest/#api-sprint-sprintId-delete

Could you provide your script?

According to my experience only the owner can see subscribers, because only the owner can manage subscriptions. A global administrator can change the owner to himself and also see subscribers.

You could query like this worklogDate > -4d and worklogDate < -1d

Kindly read the following thread https://community.atlassian.com/t5/Jira-questions/Scriptrunner-rest-end-point-create-issue/qaq-p/670374 You will find out how to pass parameters to a rest point and how to work with them. Then read the following thread…

I see, the problem is that validators work before the post function. If you set a post function, then you do not need a validator. Your post function will fill all the fields anyway.

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 CustomFieldManager customFieldManager = ComponentAccessor.getCustomFieldManager() java.sql.Timestamp…

import com.atlassian.jira.component.ComponentAccessor; import java.sql.Timestamp def optionsManager = ComponentAccessor.getOptionsManager(); def customFieldManager = ComponentAccessor.getCustomFieldManager() def parentOptionObj = optionsManager.findByOptionId(14491L); def childOptionObj =…

it must be like this import com.atlassian.jira.component.ComponentAccessor; import java.sql.Timestamp def optionsManager = ComponentAccessor.getOptionsManager(); def parentOptionObj = optionsManager.findByOptionId(14491); def childOptionObj = optionsManager.findByOptionId(14494); Map<String,Object> newValues = new…

Your code must be like this def cs = getFieldByName("Story Points") if (Integer.valueOf(cs.getValue().toString()) > 99) { cs.setError("Story Point > 99") cs.setRequired(true) } else { cs.clearError() cs.setRequired(false) } You should add the Story Points field to your behaviour and set the script for the field.

You can not fire a webhook in a post function, if an issue is deleted, because post functions fire for transactions not for issue events. You can create a webhook and define it for the issue deleted event. You can find more info here: https://confluence.atlassian.com/adminjiraserver073/managing-webhooks-867028229.html

You need to develop your own plugin, use Power Scripts to develop your own mail handler https://confluence.cprime.io/display/JJUPIN/Mail+Handler or use a email management plugin like Email this Issue or JEMH.

The answer is that you can not do it. You can not restrict available statuses, when you move issues.

What is the error?