Comments
-
What version of the plugin? What browser? Can you press F12 and check the logs in your browser.
-
Something must have changed. What do the logs have?
-
Matt. 6.3.8 is the version of jira, not the plugin. The current version is 3.0.6, which supercedes 3.0-beta-12. Jhonnatan, thanks, must not have closed the issue.
-
I'm not sure what versions that relates to. The current version of jira is 6.3.8. The plugin version with the fix has already been released.
-
Adding as an answer so this question can be closed. https://jamieechlin.atlassian.net/browse/JBHV-295 And will be fixed in next release.
-
And will be fixed in next release.
-
Atlassian haven't integrated their AOD instances, you need to create a new account. I created the ticket for you: https://jamieechlin.atlassian.net/browse/JBHV-295
-
hrm strange... i'll look into it (although not immediately). Thanks for the screenshots. Ideally could you create a ticket at https://jamieechlin.atlassian.net/browse/JBHV- you can just link back to here.
-
Can you give some version info? Any chance you could do some screenshots. For example if you take a look at the first screenshot on https://jamieechlin.atlassian.net/browse/JBHV-294, it describes it perfectly, and I don't need to read a lot of text that is a bit difficult to follow.
-
Sounds like they are not a member of jira-users, specifically, at least one of the groups with the global USE permission.
-
Dealing with this at https://answers.atlassian.com/questions/121287/unable-to-create-jira-issue-error-creating-issue-cannot-invoke-method-getvalidators-on-null-object.
-
Not really... the remote APIs aren't sufficient to copy the project to the level of detail that you get in the standard version of this plugin. I keep my eyes on developments in that space though.
-
try the CLI: https://answers.atlassian.com/questions/192/how-can-i-clone-a-project-in-jira?page=1#884
-
You can install it through the UPM - https://plugins.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner
-
You can try the script runner plugin, it has a built-in script for this: https://studio.plugins.atlassian.com/wiki/display/GRV/Built-In+Scripts#Built-InScripts-CopyProject.
-
Confluence doesn't do this, you won't be able to make it happen without major work.
-
He's just trying to set a default value... eg "Step no: " - and the user appends 99 or something.
-
That's not an error, it's just informational. Some functionality was moved around and that message is just there to help people find it. It's been there a long time though and should be removed. When Copy Project finishes is there is a message like "Project X copied to Project Y". It can take a while though depending on…
-
Surprised this is working for you - I would think you'd have the same issue as Eddie has in his question, unless I've completely got this wrong.
-
yep, JIRA 7 has some changes to the API. Thanks @Jeremy Gaudet
-
The return statement is implicit for the last line of a block. So it's correct not to use that, but there were other errors. I prefer not to use "return" if it's obvious.
-
You need to throw a new InvalidInputException if you're using a custom validator... from the way the code was written by the OP I assume it was a "simple scripted validator". In that case you just return true/false, and set the message in the UI. It's slightly simpler.
-
yes, Nic is right. I updated my answer below to take account of that.
-
Try: import com.atlassian.jira.component.ComponentAccessordef groupManager = ComponentAccessor.getGroupManager()groupManager.isUserInGroup(issue.reporter?.name, 'Technical User') || ! (issue.issueTypeObject.name in ['Incident', 'Service Call', 'etc']) if it's still not working tell us how it's not working. Beware of the…
-
Try removing your import and: def Risk_Severity = getCustomFieldValue("Risk Severity - Select").value as Integer
-
As Nic says, toInteger() is fine, or x as Integer However I would probably keep them as numeric fields, and just have a validator that the number is an integer between and including 1 and 3. That will let you do aggregate calculations on the values using script runner, or in jql if it supports it one day.
-
Just to clarify, you want to copy all custom fields on subtasks upwards to its parent (where the CF is associated with both parent and child), when any CF on the subtask changes ? Is this really useful? What happens when an issue has multiple subtasks, if the CF is changed on one, it will have the same value as its parent,…
-
Edit your workflow, add new post-function on the action of type "Script Post-function". Choose "Modify Issue" function. Enter the following code: issueInput.fields.customfield_10132 = new Date().format("yyyy-MM-dd") where 10132 is the ID of the custom field you want to update.
-
This answer is for server, not cloud But for server, you should not need the commented out bit even on create.
-
This functionality allows a bulk update to the correct "unresolved": https://studio.plugins.atlassian.com/wiki/display/GRV/Built-In+Scripts#Built-InScripts-BulkFixResolutions