Comments
-
Hello, I am not sure with what version of Tomcat comes the latest Jira update. But if you use the in-built Tomcat, you do not have to update it after updating your Jira instance. Tomcat will be updated on Jira update automatically.
-
If you create a subtask, then you do not need to add more links. Your script would look like this: subtasks(<span>key</span>,<span>"Bug"</span>).<span>size</span>();<span>return</span>
-
It is all basically the same. You need to create a listener on the update and create issue event. Then here you can find how to take the value of an option field: https://community.atlassian.com/t5/Jira-Core-questions/How-to-get-checkbox-value-with-scriptrunner-in-post-function/qaq-p/278604 Here you can find how to assign…
-
Hello, Have a look at the permission scheme of these projects. For example, my permission scheme for the Create Issues permission looks like this: * Project Role (Administrators) * Project Role (Service Desk Team) * Service Desk Customer - Portal Access * Project Role (atlassian-addons-project-access) If you want a user to…
-
Hello, You would need a plugin for it. For example, you can use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation You can create a listener on the create and update issue events with a code like this: if (#{ABC} == "456" && #{DEF} == "893" ) { assignee = "user"; }…
-
Hello, Kindly have a look at this thread: https://community.atlassian.com/t5/Marketplace-Apps-questions/Substitute-for-issueFunction-in-JIRA-cloud/qaq-p/613278
-
Hello, You would need an add-on for it. For example, you could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview There is a feature, called Live Fields. This feature can do actions on fields in the Create, Edit and Transistion screens.…
-
Hello, Try like this not (issuelinktype = 'Requirement')
-
key is a standard variable in SIL, that is why you do not need to put % before and after. But if you get a string with a key, then you need to put % before and after. You can find an example here: https://confluence.cprime.io/display/SIL/Variable+resolution Does your script work now?
-
You are welcome!
-
I do not have a ready scripts. But here are a couple of scrpts, which can help you: How to get a reference to the Epic: https://community.atlassian.com/t5/Jira-Software-questions/Groovy-postfunction-obtain-reference-to-epic-after-creating-an/qaq-p/251063 How to set Fix version for an issue:…
-
Hello, I think your code should look like this: string mainBuildKey = key; string issueSummary; string issuePriority = "Minor"; string issueDescription; string issueProject = "WIB"; string siteCode = customfield_10310; string issueType = "Sub-Task"; string[] custom_fields_mapping =…
-
Hello, Try like this: import com.atlassian.crowd.embedded.api.User import com.atlassian.jira.ComponentManager import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.user.ApplicationUsers def userManager = ComponentAccessor.getUserManager() def groupManager = ComponentAccessor.getGroupManager() def…
-
Привет, Странно. У меня из Москвы работает. Может быть, впн попробовать?
-
Hello, You would need an add-on for it, which will let you to create a scripted field. You can use the Power Custom Fields add-on for it. It is a free add-on: https://marketplace.atlassian.com/apps/1210749/power-custom-fields?hosting=server&tab=overview You can create a custom field with a script like this: if…
-
Hello, You can use also the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview There is the Live Fields feature. You can modify fields in the Create, Edit and Transition Screens. Your code would look like this: (argv["screen"]…
-
You can use ScriptRunner for it. You can catch LinkCreatedEvent and copy Fix Version from Epic to Issue
-
Kindly have a look at the plugin, which I provided. I think you can choose different colours there.
-
If my answer helped, kindly accept my answer as accepted.
-
Hello, You can not hide some system fields like fix version, status, assignee and so on in the view issue screen. That is why they will be always present in the view issue screen. But you can limit fields in the create issue screen. Go to the project settings -> screens and add required fields in the Create issue…
-
Hello, You should edit the Workflow scheme and attach the Story and Task issue types to the Defect Tracking Component driven workflow. After it you will apply changes and then all Epics and Stories will be converted to the new workflow. It will affect all your 3 projects.
-
Unfortunately, I do not know a way to do it with SIL
-
Hello, You would need an add-on for it. You could use the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could create a new custom field of the check box type, called "Send email". Then add a screen for the transition, which leads to…
-
Hello, Kindly read this KB: https://confluence.atlassian.com/adminjiraserver073/upgrading-jira-data-center-934712184.html
-
Hello, You should remove all groups, roles and users from the Create Issues permission in the project permission scheme. In this case users will not be able to create issues in this project. If this project shares permission scheme with other projects, then copy this permissions scheme first, remove all users, groups and…
-
Hello, What do you man by "once epic chosen"? What does it mean "chosen" in Jira terms?
-
Hello, Check that firewall in Windows is off
-
Hello, You would need a plugin for it. For example, have a look at the ScriptRunner plugin. Here is more info: http://scriptrunner-docs.connect.adaptavist.com/jiracloud/enhanced-search.html#_issuesinepics
-
Hello, are you sure that that the user, under which you try to log time, have the Browse Issues permission in this project?
-
Tranisitions are entities of workflows. And you attach workflows to projects. Projects do not have any statuses. Issues have statuses. That is why you transition issues, not projects. If you want to know all transisitons for a project, then you have to choose all workflows for a project and then choose all transitions…