Alexey Matveev Expert

Admins can do anything in the name of another user. I am not sure if it is logged somewhere. Maybe you can find this function and look in the source code of ScriptRunner. There could be debugging messages. You could set debug logging level for the package of the script. 

Your script is too long. I would advise you to make it shorter and try to save a value in the assignee field. Make the short script work. After it you can fix your long script.

You can use such plugins as Structure or Big Picture to organize your issues in hierarchy.

What exactly do you want to do? Yes, there are no logs in the changelog on creation.

Push the search icon and you will see your favourite filters.

JQL can retrieve only issues. You can not retrieve time. You would need to create a custom field, where you would count the time, by using such plugins as Power Scripts or ScriptRunner. Or you can use Time In Status plugin.

I just checked. I have the same behaviour. I guess, it is a feature:)

I guess, it is all static compilation. Moreover your code seems to me as broken. I am not sure it will work at all. import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.user.ApplicationUser; import com.atlassian.jira.user.util.UserManager; import com.atlassian.jira.security.groups.GroupManager;…

It will show you tickets, which are not currently in status Resolved In Trunk, because you could change the status later. If you want to find issues, which are still in the Resolved In Trunk status then you should write a JQL query like this: project = "Online Application v4" AND status changed TO "Resolved In Trunk" by…

I think you need to filter issues by a project and then find out which issues cause the problem. There is no easy way.

what do you mean by "list of step"? If you want to store data in the Jira database then use Active Objects

What are the errors?

You should go to the project settings, choose Request Types and delete the required request type:

Check in validator what kind of subtask you have and check the required fields for this subtask type. Basically, if you make your process complicated then you have to make complicated solutions.

If you want to create a subtask then you should use the Create Sub-Task option In Jira Server/ Data Center it is under the More menu.

Try to do it like this: status changed from New to Assigned DURING (startOfDay(-3), now()) by user

I am glad you solved the problem

You can attach a validator to the transitions and check if the required fields are not empty.

You are not using behaviours the right way. You should set values with setFormValue method. https://scriptrunner.adaptavist.com/latest/jira/behaviours-api-quickref.html

I do not understand what you mean. But you can link a sub task to another task. It is fine.

You would need an add-on for it like Time In Status: like https://marketplace.atlassian.com/plugins/com.obss.plugin.time-in-status/server/overview

Sub-tasks do not have impact from the parent task

Try like this import com.atlassian.jira.ComponentManager import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.user.ApplicationUser import com.atlassian.jira.user.UserPropertyManager import com.atlassian.jira.issue.IssueManager import com.atlassian.jira.event.type.EventDispatchOption class…

I think your JQL query must look like this status changed from "Ready For QA" to "TO DO"

You would need an add-on for it like Power Scripts or ScriptRunner. These add-ons let you automate Jira by writing scripts. Power Scripts uses its own language called SIL and ScriptRunner uses groovy.

You can have a look at the Big Picture add-on https://marketplace.atlassian.com/plugins/eu.softwareplant.bigpicture/server/overview

It is not on the initialiser. You must add Severity and Frequency fields to the behaviour and put the script for the both fields.

You can download a CSV file and open it in Excel. You can find more info here https://confluence.atlassian.com/jiracoreserver073/working-with-search-results-861257284.html

I think you would need an add-on for it like Power Scripts or ScriptRunner to set the value of the fix Versions field to null when an issue moves to the TO DO or Review status.

You do not need to handle authentication. You can find more info here: https://developer.atlassian.com/server/framework/atlassian-sdk/developing-a-rest-service-plugin/ Read about @AnonymousAllowed annotation.