Alexey Matveev Expert

You would need to create a scripted field with a code which would go through all necessary links from the current issue and sum up all the story points. The script would depend on the links you use.

Hello, Yes, it can calculate working time with subtasks. When you are on the detailed issue view you should enable the Include Sub-tasks checkbox in the Time Tracking panel. The settings only works for the detailed issue view

Hello, Make sure that your databse uses UTF-8 encoding and Jira also uses UTF-8 encoding.

Hello, You can configure the colour of the cards. You would need to go to the board configuration menu and choose Card Colours and in the Colours based on field choose Queries. You could enter duedate > startOfDay() and duedate < endOfDay() and set the red colour for it. As for the labels "Today" and "In 3 days" you could…

 If you use Configiration Manager plugin then you can choose migrate to a new project option and provide a project key and a project name.

Hello, Yes, it is possible. That is what we usually do. We write a code and execute it in the Adaptivist Scriptrunner script console.

Try UserUpdatedEvent or UserEditedEvent

I think your script works as expected. If a user is created it does not mean that the user was added to a role. I would look for another event. I do not have access to Jira right now. I ll have a look later.

The question is publicly available. What do you mean by #it does not work in automation#? What is automation? You log script variables. Did you check in the log that the variables have correct values in automation?

Hello, You need an add-on for it. For example Automation for Jira. You could add the Manage Watchers action there https://marketplace.atlassian.com/plugins/com.codebarrel.addons.automation/cloud/overview Or you can use Adaptivist ScriptRunner and write a post function or a listener. But you would need to do some coding.…

It would be something like this project = ABC AND issuetype in (Parent, subtask) AND (issuefunction in parentsOf("\"User Picker\" = user1") OR (issueFunction in subtasksOf("project in ('ABC')") AND "User Picker" = user1)) ORDER BY issuekey ASC

You can create a scripted field as @Tarun Sapra suggested. You would need an additional add-on for it and do some coding but it is not connected to JQL. JQL just finds issues but you can provide information about the issues in custom fields.

Hello, It is not possible. JQL queries can return only issues, they can not return number of times.

Good to hear

Hello, I think it is not about the Jira Service Desk Api, but it is about the curl. You can find posts with the same problem https://stackoverflow.com/questions/4514199/how-to-send-double-quote-in-d-parameter-for-curl-exe

Hello, Go to the Field Configuration for the project and set the Default Text Renderer for the Description Field.

With Jersey Client ClientResponse response; String auth = new String(Base64.encode("username" + ":" + "password")); final String headerAuthorization = "Authorization"; final String headerAuthorizationValue = "Basic " + auth; final String headerType = "application/json"; Client client = Client.create(); WebResource…

Hello, The field due date will be shown on an issue screen only if the user has the Schedule Issues permission. Also you need to add the due date field to the screens on which you want to see the field. For marking issues you would need an add-on like Colors For Jira add-on…

Try like this project = ABC AND issuetype in (Parent, subtask) AND (issuefunction in hasSubtasks() OR issueFunction in subtasksOf("project in ('ABC')")) AND "User Picker" = user1 ORDER BY issuekey ASC

Hello, What do you mean by issues with user2, user3 etc. You mean that user2 is in the User Picker field for the issue?

Hello, You should add the Story Points field to the view and edit screens. In this case you will be able to edit the field on the detail issue view screen.

I guess your Jira Version is less than 7.x.x, is not it? Try this script import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue import com.atlassian.jira.ComponentManager import com.atlassian.jira.issue.CustomFieldManager import…

Yes, It is from the version 7.6. But I guess that is the version you are using

You should put the script last in the post function list. Could you provide a screenshot for the create transition with all the post-functions?

I am afraid there is no documentation. You just try to restrict your comment to a group and check what is returned.

Could you provide your pom.xml? Usually spring-scanner is included there. There must be something like this <dependency> <groupId>com.atlassian.plugin</groupId> <artifactId>atlassian-spring-scanner-annotation</artifactId> <version>${atlassian.spring.scanner.version}</version> <scope>provided</scope> </dependency> Then you…

I really do not understand the architecture what you are doing there. Your question was about the error in your script. I answered about the error. The problem is that you should initialize the issue. How you do it depends on how the whole thing, you are developing, works. If you want your code to work, you should pass to…

You should provide "DEVOPS-1". It should work after it. Of course the issue with the key DEVOPS-1 must exist in your Jira instance

In ScriptRunner your script would look something like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.project.Project import com.atlassian.jira.project.version.Version def projectManager = ComponentAccessor.getProjectManager() def projectSource =…

Issue.getProjectObject() will not work. You need to get a reference to an issue first. For example def issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("STAR-1") and then you can use def actors = projectRoleManager.getProjectRoleActors(role, issue.getProjectObject())