Alexey Matveev Expert

I noticed that your plugins do not startup within 60 second. You can increase waiting period for plugins to start up. You should add <startupTimeout>12000000</startupTimeout> to the configuration section of maven-jira-plugin in your pom.xml <plugin> <groupId>com.atlassian.maven.plugins</groupId>…

Then you need to add the issue created event. I do not know if you need it or not, but you will not be able to distinct the incident movement event from the incident creation event because if you move an incident, the create event fires.

Ok. You can not use attachmentManager.getAttachments(issue) to get the newly added files to the issue. This method get attachements from already existing issues that is why if you look in your logs you will see NPE. If you want to get newly added files then follow this guide…

The problem is that a validator must return true or false. Your validator returns null. And your validator never works. You should do something like this def flag = true attachmentManager.getAttachments(issue).each { if (!it.getFilename().endsWith(".xlsx")) { flag = false; } } return flag I did not check the code. But I…

I found it. You did not initialize Map<Option, Boolean> issueLinkMap; You should do like this Map<Option, Boolean> issueLinkMap = new HashMap<Option, Boolean>();

Did you check in the log file? linkedIssueDomain is null or not?

Hello, Your rest expects JQL query from you. customfield_14729.value = "AA: Analytics " is not a valid JQL query. Open issue navigator and write a valid JQL query. In your case you need to find the name of the customfield_14729 and write something like this "the name of your custom field" = "AA: Analytics "

What validator do you use? 

Hello, I think the problem is because linkedIssueDomains.iterator().next() returns null. You log "log.warn("linkedIssueDomain : " + linkedIssueDomains.iterator().next());" The problem is that in the log it can be not null. But when you assign it to a value it can be null because iterator().next() takes the next element…

It shoud be like that attachmentManager.getAttachments(issue).each {(it.getFilename().endsWith(".xlsx"))}

Hello, What is the error?

Then you would need to wirte something like this (not status changed from Open to "In Progress" before -48h) OR (not status changed from "In Progress" to Test before -48h) and so on. You would need to put all possible transitions from one status to antoher.

Component is an out of the box field in Jira. You can define components for a project. For each component you can defined a default assignee (Component Lead). Then you can put the Component field on the create, edit, view or transition screens. You can read more on how to work with the Component field here…

Hello, If you have your code somewhere in Github or Bitbucket it would be nice to have a reference to it so that it could be executed and checked

If you have Adaptivist scriptrunner then you can write a post-function. Or if your first connected field is Component then you can provide a default assignee for each component and in this case you do not need to do any programming. 

Hello, I am not sure what you mean by "moved". You can use the standard automation functionality in Service Desk. Define the event when the trigger must work (define the work "moved"). Add issue matches condition and write something like this "yoursla field" = remaining("5m") and created = -5m Then add the Transition Issue…

Hello, There are only two levels out of the box. You would need to create your own custom field. Or use Adaptivist scriptrunner behaviours to connect several fields. But the solution would be messy (too much code for a behaviour)

It is ok. You executed atlas-clean which will delete your target folder but it can not delete C:\Applications\Atlassian\myPlugin\target\myPlugin-1.0.0-SNAPSHOT.jar file in the folder. A process is blocking it. If you do not know which process blocks it then restart your pc

Ok. And what is the result?

Try Ctrl-D atlas-clean atlas-run

Hello, I think it means that something already uses the 2990 port that is why Jira tries to instantiate itself on another port. The port is written in the logs. Try to use the prot from the logs not from the tutorial

You can enter this query in the Issue Navigator and see the results. You can create a filter from the query and use the filter in the Jira gadgets

Hello, Your Jql would look like status changed from done to "selected for development" during ("2017-12-01 10:00","2017-12-02 10:00")

Hello, As far as I know stories are estimatied in story points and tasks are esitmated in hours. In this case you get everything you want. Do I understand correctly that you want to sum up all logged work for an issue and set the value for the Original Estimate field?

Your requirement is to show all issues where statuses have not been changed for more than 48 hours. That is why there are only issues in the open status. If the Open status was changed to something else, then the status of the issue was changed for more than 48 hours. You need to reformulate your requirement. Do you mean…

Hello, Try like this not status changed before -48h

Hello, Kindly read the KB https://confluence.atlassian.com/jira060/how-do-i-assign-issues-to-multiple-users-370705091.html

If you use 13921L then you should use customFieldManager.getCustomFieldObject(13921L). But if you have serveral environments for Jira (dev, test, prod ) then it is better to reference your field by Name customFieldManager.getCustomFieldObjectByName("fieldName"). And if you use getCustomFieldObjectByName it must be the…

You need to convert Object to Timestamp. And you incorrectly initialize custom fields. It should be like this import com.atlassian.jira.component.ComponentAccessor import java.sql.Timestamp def customFieldManager = ComponentAccessor.getCustomFieldManager() def tamamlanmaTarihiCf =…

Hello, Could you provide the whole script?