Comments
-
You want to say that you use the Create a sub-task post function and add this line into the Additional Issue Actions. Try to use Issue.setCustomFieldValue(CustomField customField, Object value) after the issue.assigneeId = user line. You can find more info here:…
-
This a plugin for Spring scanner 1x. It seems, that you wrote everything correctly. I need more time to dig dipper, but unfortunately, I do not have time right now for it.
-
What do you mean by the new issue? Do you mean that you get an issue in your post function and change the assignee field for it? If so, then it is correct that your values are not saved. Or you mean that this post function is on the create transition? Then you should put your post function last in the list and add the…
-
Если есть скриптраннер или пауер скриптс, то можно создать скриптовое поле, которое будет из истории получать данные о количестве переход из одного статуса в другое. А дальше в JQL отбирать по этому полю. Другой вариант написать свою JQL функцию на тех же плагинах.
-
Kindly make sure that the new filter for the board is shared with the user, who can not see the board.
-
You can go to System->Events and You will be able to see, where these events are used.
-
Open the required transition post function and have a look at what event is generated on the transition. Moslty it is the Generic event. If so, then make sure that you set users for the Generic event in the project notification scheme.
-
If my answer hepled you, kindly accept my answer so that other people could find this answer, if they have a similair question
-
You can find info on how to add a custom field to the Issue Collector form here: https://confluence.atlassian.com/adminjiraserver071/advanced-use-of-the-jira-issue-collector-802592648.html
-
Try to write like this relVersion_int.updateValue(null, issue, new ModifiedValue("", [issue.getCustomFieldValue(relVersion_int)]), issueChangeHolder);
-
What is line 34 in your script?
-
The only way to retrieve a deleted custom field is to restore your Jira form a backup.
-
First you need to run the atlas-mvn package command. Then there will be 3 files in the target folder. Open your Jira and go to System-Add-ons->Manage add-ons and click the Upload Add-on button. Then choose either the <yourplugin>.jar or <yourplugin>.obr file from the target folder of your plugin and push the Upload button.…
-
Jira does not manage only Agile projects. You can manage non Agile projects as well.
-
Try to add jersey-client dependency as it is provided here: https://community.atlassian.com/t5/Questions/Jira-plugin-using-Jersey-client-for-REST-call-to-external/qaq-p/431144
-
As far as I understand from your previous message the problem was with the issue variable. How do you initialize the issue variable? Where do you run the script?
-
Errors will be in the atlassian-jira.log. You can find more info here: https://confluence.atlassian.com/jira063/where-are-the-application-server-logs-683542381.html
-
What was the error?
-
1. There can be a master user. 2. You can use Jira REST Api to create an issue. You can find more info here: https://developer.atlassian.com/cloud/jira/platform/rest/
-
I am not sure, I understand your question. First, you need to add the Strategic Objective field to your behaviour. Then your attach your script to the added field. Your script works after you selected an option in the Strategic Objective field.
-
ScriptRunner works only after you selected an option in the list, not in the process. I guess, you can not change it.
-
If the user can see the issues, when logged in to Jira, then the user must see the issues through the Rest Api. There is no additional permissions. Make sure that your REST call is correct.
-
Boards just represent the state of your issues, that is why if the state of an issue changed, it will change on all boards. For example, you have an issue in the New status and then you moved this issue to the In Progress status. The issue will move to the In Progress status on all boards and as a result the issue will…
-
Only Jira Administrators and Jira System Administrators (for the Jira Server Version) can delete projects. You should set these permissions only to the users, whom you trust as Jira admins. You can find more info here: https://confluence.atlassian.com/adminjiracloud/managing-global-permissions-776636359.html
-
You should have a look at your workflow settings. There must be a transition available from the Complete state to the Open state. If such a transition is not available, then you should create it. Kindly read the following documentation:…
-
You write a script and put in in JIRA_HOME/scripts directory. Then you create a service according to this guide https://scriptrunner.adaptavist.com/latest/jira/services.html
-
You can not execute behaviour as a script. Behaviour requires html browser to be run, but your script will work in the server. You usually save scripts in JIRA_HOME/scripts folder
-
You would need a plugin for it like Issue Matrix.
-
What is the error? Did you add the Test request type to the behaviour and add the script to the field? Kindly log info into logs and see the logs import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.customfields.manager.OptionsManager import…
-
Kindly make sure that you publish the workflow.