Alexey Matveev Expert

Click the edit button and see if the duedate on the edit screen

As far as I inderstand there are 2 addons which can help you Adaptivist ScriptRunner with the behaviour functionality and Power Scripts with the live fields functionality. Each of them has own advantages. But you would need to answer Nic's question about the Database Information field. What kind of field is it?

What is your Jira version? And in what custom field of the Task issue you want to see the summary of the Bug issue? Moreover I guess you can see now the summary of the Bug issue in the link web panel of the Task Issue. I mean when you enter the detailed view of the Task issue you can see the linked issues with the Task…

The problem is that you said you want a script for Jira 6 and Jira 7. In Jira 7 you can use UserSearchService which will let you filter users before retrieving them. I am not sure if UserSearchService will work for you Jira 6 version. That is why when you filter the appUsers list check if a user is active by isActive…

the field summary is defined for the issue object not for issue types. Do you want to say that you want to copy the summary field from one issue to another? On what event do you want to copy it?

Filter the appUsers list as you wish. I do not think your Jira crashes if you get the full list first.

Hello, Do you mean that you have Adaptivist ScriptRunner add-on and you want to get the issue summary in a post-function or validator? If so, it would be like this issue.summary

I also began to learn Power Scripts. In case it can be useful. If you have Power Scripts plugin, you can add a post function with a code like this #{text_single_line_field} = currentDate() - created; It would do about the same.

You need to create a post function with a script like this import com.atlassian.jira.component.ComponentAccessor import java.util.Date import com.atlassian.jira.issue.util.DefaultIssueChangeHolder import com.atlassian.jira.issue.ModifiedValue def csDays =…

Hello, The duedate field must be added to the edit screen for the issuetype and the user must have the schedule issues permission.

Hello, Do you mean that you use REST API? JQL would look like description ~ "this text" Then you could use search rest call to get all issues by providing the query above jira/rest/api/2/search?jql=description ~ "this text" then you can iterate over received issues and update them as you updated before.

I guess your question is solved. Good luck:)

I guess People tab does the same for JiraCloud. Did you try to setup with the People tab and it did not work?

Hello, You would need an addon for it like Adaptivist ScriptRunner or Power Scripts

Hello, Roles are defined for projects. If you grant permissions based on project roles then the permission will be granted to the users who are defined for the project role in a certain project. You can use the permission scheme for multiple projects and only users defined forthe project role in the project will have this…

You should ask Adaptivist ScriptRunner support not Atlassian. If you find out what was the problem kindly provide your answer here. I would like to know the answer as well. Good luck! :)

I gave you a link on how it should work. As I said in my previous post I was not able to make it work on the Create screen within 20 mins. Maybe it is not supposed to work for the Create screen. I would like to help you but unfortunately I do not have time right now. I would advise you to ask Adaptivist ScriptRunner…

Hello, Do no add an issue via database. It is not the way it should be done. Use REST API instead: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-issue-post

Hello, Try to add your own parameter to webhook. It would look something like this: http://example.com/rest/webhooks/webhook1?myparam=2 You would define a different myparam value for each webhook. In this case you would know which webhook was triggered.

Jira Software does not have such functionality

Hello, If you have Adaptivist Scriptrunner, you could use linkedIssuesOfRemote function. You can read more information here: https://scriptrunner.adaptavist.com/latest/jira/jql-functions.html#_remote_issue_links

Hello, Try something like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.security.login.LoginManager LoginManager loginManager = ComponentAccessor.getComponent(LoginManager.class); Set<ApplicationUser> appUsers = ComponentAccessor.getUserManager().getAllUsers();

Hello, Kindly try \n

Hello, If you have Scriptrunner, you could do it with the behaviour functionality (available only for Jira Server/Data Center) or custom validators.

Hello, I guess what you need is SLA functuinality. There is SLA functionality in Jira Service Desk. If you do not have Jira Service Desk then look for SLA plugins in the marketplace.

Hello, If you are on Jira Server or Data Center, you could use behaviours of the Adaptivist Scriptrunner plugin

I see. Then there is the new UI experience. I do not use it. In the old UI experience the field still exists.As far as I know there are means to switch the new UI experience to the old one

Are you on Cloud?

You should use getFieldByName to get your custom fields def cs1 = getFieldByName("customField1Name") def cs2 = getFieldByName("customField2Name") then you should check the value and set the other field to required if (cs1.getValue().equals("value")) { cs2.setRequired(true); } else { cs2.setRequired(false); }

You should not provide the same database name. It does not work like that. Install Jira and Confluence in different databases. Then choose SSO provider and cofigure it. Or use Jira user directory as the user provider for Confluence