Comments
-
What is the response code?
-
I am not sure how you send your request. But there is always a response. I usually use SOAP UI to play with REST calls.
-
But It could be done out of the box. You should create a field scheme configuration for the Bug issue type and set there the custom field required. https://confluence.atlassian.com/adminjiracloud/changing-a-field-configuration-844500798.html
-
Yes, you can use scriptrunner to make a field required for an issue type. You can either use behaviours or validators. If you use a validator, you would add a validator to the create transition. In this validator you would check issue type and if it is a Bug, you would check if the required field is set with a value.
-
To update priority you should use PUT rest/api/2/issue/{issueIdOrKey}. https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/?_ga=2.226925854.2030217466.1525875113-593458345.1525875113#api/2/issue-editIssue Example of JSON would be like this: {"update":{"priority":[{"set":{"name" : "Trivial"}}]}} To update a status…
-
You can have single screen scheme for all issue types but you would need Power Scripts Live Fields or ScriptRunner behaviours to hide a custom field depending on the Issue type.
-
Kindly read the following KB https://confluence.atlassian.com/bamboo/restoring-passwords-to-recover-admin-users-289277354.html
-
You can check whether a user is active or not by the isActive() method in the ApplicaitonUser class. If a user is inactive, you should not send a email.
-
I just checked and the Create issue event always returns Create. Could you provide logs and your final script?
-
You add logging by log.error. That is the simplest one. You do not have to set logging levels. For example, if you want to see the verticalValue value then you can do like this: def allowedOptions = null def optionsManager = ComponentAccessor.getOptionsManager() def customFieldManager =…
-
I still strongly believe that you provided wrong names for fields. You should put logging in your script and have a look what is going wrong.
-
You can use ScriptRunner behaviour. You can find an example here: https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html#_example_setting_up_a_hidden_field
-
Rank is different from the Priority field. They are not connected. Rank is a global field across all projects, that is why issues from different projects can still be ranked. Priority is just a field. It is not connected to ranking.
-
Rank is different from the Priority field. They are not connected. Rank is a global field across all projects, that is why issues from different projects can still be ranked. Priority is just a field. It is not connected to ranking.
-
Hello, You can find an example here: https://community.atlassian.com/t5/Jira-Core-questions/Copy-Custom-field-value-from-one-field-to-another/qaq-p/73207 If you write a listener then instead of issue use event.issue
-
Hello, There is no difference between deleting a subtask and a task. You need the Delete Issues permission in the project permission scheme. That is all. Then you open a subtask in the detail issue view and choose More->Delete
-
You can write a scripted post function in scriptrunner. You can see an example here: https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-auto-create-multiple-subtasks-in-JIRA-by-groovy/qaq-p/559686
-
You have to attach the script to the vertical field, which means that getFieldChanged() returns a reference to the vertical field. That is why your code should look like this: def allowedOptions = null def optionsManager = ComponentAccessor.getOptionsManager() def customFieldManager =…
-
then you should use setFieldOptions instead of setHidden. You can find an example here: https://scriptrunner.adaptavist.com/latest/jira/behaviours-api-quickref.html#_formfield_setfieldoptions_iterable
-
It should be like this: def version = ComponentAccessor.getVersionManager().getVersion(issue.getProjectId, "ABC"); issue.setFixVersions(Arrays.asList(version))
-
You can pull tasks up and down in the backlog and sprints. That is how you rank your tasks. Or you can use the Priority field.
-
It should be like this def vertical = getFieldByName("vertical") log.error("vertical: " + vertical) def verticalValue = vertical.getValue() as String log.error("verticalValue: " + verticalValue) def typeOfEngagement = getFieldByName("type of engagement") log.error("typeOfEngagement: " + typeOfEngagement) def…
-
Are there any errors in the atlassian-jira.log file?
-
Try to use def linkedIssueString = <span>request</span><span>.</span><span>getParameterValues</span><span>(</span><span>"</span>issuelinks-issues<span>"</span><span>);</span>
-
You can use Jira Rest Api GET /rest/api/2/issue/{issueIdOrKey}. It will return all worklogs for an issue. You can build your report using this data. https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/?_ga=2.164410812.2030217466.1525875113-593458345.1525875113#api/2/issue
-
Do your teams work in the same project? If no, then you can make different workflows for each project and automate each workflow as needed by each team.
-
You should add the User Is In Role or User is In Group condition to the required transitions. You can read more about conditions here: https://confluence.atlassian.com/jira060/advanced-workflow-configuration-370705899.html
-
You can not do it out of the box. Maybe there is a plugin available. Look at the Portfolio plugin.
-
Hello, you should provide JSON with your REST call, in which you pass the value: {"value":"your value"}
-
You can either create another listener or use the same one. But you need to define in the listener whether the event issue is a sub-task or the parent task and then code different logic. For parent task you would iterate over sub-tasks and set the fix version for the sub-tasks (that is what your script does right now) For…