Alexey Matveev Expert

You need to choose an SSO provider and set it up. You would need to cofigure Testlink and Jira for the provider. I do not know how to configure Testlink, but for Jira you should look at the following plugin: https://marketplace.atlassian.com/plugins/com.resolution.atlasplugins.samlsso.Jira/server/overview

Do you mean that there is no Time Tracking field there? Then check if time tracking is on. You can read more info here: https://confluence.atlassian.com/adminjiraserver072/configuring-time-tracking-828788203.html

You can accept your own answer. Just make an answer and accept it :)

Why you do not want to use Jira Rest Api. You could execute a jql query with GET /rest/api/2/search and get all the issues. You can read more here: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-search-get

It looks to me that your json is not valid. At least it must be like this: args: fields: customfield_XXXXX: { value: '{{foo.stdout}}'}

If the gadget, which you use, does not support a parameter, which will let you set the "Created Date" field, then you can not set it in your Dashboard. All you can do is to set it in your filter.

If you have the hello world message, then your script is loaded. All you need to do is to write a script, which will work for you.

There must be three dots. You can see them in the screenshot below

You should go to the Board Configuration -> Card Layout and add the Lables field for the Active sprints

Or you could link the issue from the Confluence page and you will have the "mentioned in" link in the issue detailed view.

Do you use the version functionality of Jira? https://confluence.atlassian.com/adminjiraserver/managing-versions-938847201.html If so then there is a field called Fix Version and it is a multi select field. You can attach one issue to multiple versions. But anyway it seems odd to me, that you solve one issue in multiple…

Do you mean, that you want to see all issues that are blocking other issues in a swimlane? Like in the picture 2? If so you could use Power Script, ScriptRunner or something like this to create a Query swimlane. For example, in ScriptRunner you could use issueFunction in hasLinks("is blocked by")

You need to execute GET /rest/api/2/issue/{issueIdOrKey}?expand=changelog You will see in the result all status changes with dates. Unfortunately, the time, which was spent in each status, you should calculate yourself. You could subtract the date of the current status with the date of the previous status.

I am not sure how you are going to make a web-page using ScriptRunner. Could you tell me a bit more about methods that are deprecated? Could you mention their names (some of them)?

I do not understand exactly what you mean. First of all, if you update an issue with ComponentAccessor.getIssueManager().updateIssue(user, mutableIssue, EventDispatchOption.ISSUE_UPDATED, false) Then Jira will automatically change the update time of the issue. I guess, you do not want it. Then you have to change it back to…

You need to use an add-on. For example, Easy Links For Jira: https://marketplace.atlassian.com/plugins/com.codedpoetry.easylinks.easy-links/server/overview

You would need to use several rest calls. 1. You need to define when the required sprint started. You can do it with GET /rest/agile/1.0/sprint/{sprintId} 2. You should find all issues in the sprint GET /rest/agile/1.0/sprint/{sprintId}/issue 3. You should iterate for all issues in the number 2 and compare the date when…

Ah, that is right.

Or maybe you can make a status called Draft. And then a user could submit a request with few data as possible. And then he could fill all the required data during the draft status. After it the user could move the issue to another status.

I think it is called federating Jira instances. You can read more info here https://confluence.atlassian.com/enterprise/federating-jira-managing-multiple-instances-461504624.html

Do I understand correctly, that after you filtered issues, which were added after the Srpint started, you also want to see the exact date in a column, when the issue was added? If so, then as far as I understand you have Scriptrunner. You can create a scripted field which would return to you such a date. On the other hand…

I do not know about a Linked Issue Field out of the box. I guess you use an add-on. What kind of add-on do you use for the field?

If a user does not have a Jira software license, he can still view any service desk or core projects but he will not be able to use boards. If you do not want a user to see a project you should not grant the user browse issues permission. You can read more about how to grant permissions here:…

And also kndly make sure that your user is a jira software user. You can go to User Management, find your user and in the Applications column you should see Jira Software

ah, you mean long in size (I though long time). I got it :) Yes, you can use Jira Service Desk Rest Api to develop your own application or look in the marketplace maybe there is an add-on available.

the Organizations field is a feature of Jira Service Desk that is why it can not be used in Jira software. For example, like in Jira software project you can not define SLA and do not have Automation.

You can develop an application and submit requests through Jira Service Desk Rest Api. You can find more info here: https://developer.atlassian.com/cloud/jira/service-desk/rest/ But what exactly takes long time currently? Does the portal loads long or when you submit a request it takes long? Do you have any add-on…

I can not see anything bad concerning your problem in the log. Could you go to coq wheel -> Applications -> Versions and Licenses. Kindly check if your license is ok.

As far as I understand there is only one question left. How to make the script more generic because right now you have an issue key defined in the script. It would depend on how you want to launch your script. Is it a scripted field , validator, listener or you want to launch it just from Script Console?

You should change def dateFieldObject= customFieldManager.getCustomFieldObject('Live Date'); def dateFieldObject2= customFieldManager.getCustomFieldObject('Collections Start Date'); to def dateFieldObject= customFieldManager.getCustomFieldObjectByName('Live Date'); def dateFieldObject2=…