JamieA Expert

Which is line 31? Can you log the updateIDValidationResult, what does that show ? It should have methods like getErrors or getErrorCollection to find out what went wrong, but the toString() result may well have that. Is the custom field on the screen for the sub-task? None of the reindex code should be necessary btw.

This is tricky but doable. But you need the jql functions from the script runner plugin (couple of other plugins can do similar to be fair). The query is like this: status != Done and issueFunction in linkedIssuesOf("status = Done", "has epic") and not issueFunction in linkedIssuesOf("status != Done", "has epic") To…

You will need to look in the application log file and see what if any errors preceeded that. You can post anything relevant here... I personally won't spend much time looking at this as your jira version is out of support.

So that shows you that the script is working at least up to line 7, if 2012-07-31 00:00:00.0 is actually the value of the Starting Date custom field. Continue onwards adding debug lines. It looks to be the same problem you had before, ie: CustomFieldImpl.getDefaultValue(...) (which is near the end of your stack trace). Can…

Get a fresh install of the version you had, and diff your jira-app.props with the one in the clean install.

Yeah you can do that... not all the properties are valid so it's worth reviewing each one that you've customised.

Correct, because they would not implement it threw throwing an InvalidInputException. I agree, it should be reopened.

Oops sorry, meant to link to your q in my answer.

You can't... any validator that fails logs a stack trace. It's a pain... In fact I see there is a q for this already, and a bug marked "won't fix"

For the onresolve link there is an updated version of the script at https://studio.plugins.atlassian.com/browse/JBHV-90.

This is non-trivial. IIRC I've done this before. The way to do it is create a normal multi user picker field. Then in the behaviour initialiser you specify where it gets its suggestions from, which is a rest endpoint, namely: /rest/api/1.0/users/picker. This lets you provide parameters to specify the project and role to…

I see similar problems with 2.9... it grinds to a halt every 2 or 3 days.

> Is there something I could use to avoid this? You could upgrade.If you can't upgrade then you could use script runner to rename them... but I can't remember the API, it changed substantatially for Options around 4.4 iirc.

What's wrong with disabling the options? That's the best solution.

Thanks, don't know why I couldn't find that. It kind of sucks that team calendars could not have an upgrade task to do this.

OK here they are: https://plugins.atlassian.com/server/1.0/download/pluginVersion/424566 From this one extract the groovy_all_...jar from the /embeddable directory and put it in web-inf/lib. http://dist.groovy.codehaus.org/distributions/groovy-binary-1.8.1.zip

I had already given it, or you could have found it with about 20 seconds internet research, but here it is again. https://studio.plugins.atlassian.com/wiki/display/GRV/Script+Runner. Top of the page. Note that Eva's link is actually the source jar.

You only need to restart once. Put both jars, ie groovy-runner-N.N.N.jar and groovy-all-N.N.N.jar in web-inf/lib. And make sure they are not in <jirahome>/plugins/installed-plugins.

You did not do something right. It's not that difficult if you approach it methodically. Anyway, good luck with python.

Undo everything you have done, then follow each instruction here carefully: https://studio.plugins.atlassian.com/wiki/display/GRV/Script+Runner#ScriptRunner-Installation

What Nic is saying is correct. Get the issues with candidate worklogs then filter the worklogs further, eg: import com.atlassian.jira.component.ComponentAccessordef worklogManager = ComponentAccessor.getWorklogManager()def startDate = Date.parse("dd/MMM/yyyy", "01/Dec/2016")def endDate =…

Have you looked at the docs: https://developer.atlassian.com/display/SPEAK/Speakeasy ?

I have seen something similar. It's a bug, you should report it via a support request. The raw HTML may be be helpful, it's probably a css/javascript issue.

Thanks for your answer James.

There are two answers... there is an undocumented (currently) rest API where you can call any script via a rest request, if you have admin permissions. I'll give you code examples for both of these but they are ugly code just lifted from something I may have been once working on, not exemplars at all. So here is an example…

Possibly a bug in confluence 4.0? Ie the css fails to take into account the size of banner when drawing the editor and footer etc. Sorry for being so vague but I've had similar problems before.

I don't see a screenshot...

You've written this as a behaviours script. That's the bestway to do this, although it could also be done as a validator. Can you send a screenshot of the config.

Try getFieldById("duedate") But note you have nothing that sets the due date back to not required, if the user changes from option A to something else. So remove your "if" block and use: getFieldById("duedate").setRequired(getFieldByName("End User").getValue() == "A")

Using com.atlassian.jira.issue.AttachmentManager. But why do you want to copy them if they're on the parent...?