JamieA Expert

maybe you have a trailing space or something on your status name. Is the condition tester there? If so try:assert issue.statusObject.name == 'Approved-Company Car'(just to test) and post the output.

issue.getStatusObject().getName() is exactly the same asissue.statusObject.nameYou don't specify any key because you have the issue in the "issue" variable...

Nic - I don't blame the people, most times I've seen this is jira -> jira export import using CSV. It creates a resolution called Unresolved. That is the bug. And so the prevention would be simple enough, prevent creating a resolution with the word that is used to display Unresolved, in all languages, and map that word to…

I didn't type much because I didn't want to steal your thunder. Atlassian really need to fix this one, it must have bit so many people.

ouch. If you need to fix that you can try: https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-BulkFixResolutions

The ids are wrong. The FieldArea itself will not change, just the input element within it.

On what field have you added that server-side script?

We also have had this problem... across all the IE users. I thought the certificate might have expired but it hasn't. We don't get a blank screen, just a message saying sthg like "you must accept the security certificate for this applet to run" but no prompt to actually accept it.

Nic is correct as usual, but I don't think that's the problem. I did a quick test and it seems like jira requests the value of the custom field even when it's not in the context. I don't know why... I think there is a reported bug for this in jamieechlin.atlassian.net/browse/GRV but it's not fixed, because I'm not sure…

issueFunction in commented("by currentUser()") works fine in recent versions.

Also commented jql function in script runner. This will just find issues where the specified user commented, and not "participated" in as the Participants field gives you. I appreciate you can't install plugins but maybe someone else has the same question. AFAIK you can't do it without a plugin.

Can you give a bit more detail - is this your own script or some of the built-in ones?

Not through SOAP, but IIRC there is a REST API. Get the "rest api browser", then you can easily see what all urls it provides.

> it's weird to have a different server behavior depending on the browser I agree, it is weird. So the page source is actually different? You expect some minor differences like diff stylesheets, but not that.

I don't think they should appear in the <head> section, they should be added to batch.js. You can disable this by adding the element: <param name="batch" value="false"/> to your <resource> element. Or in dev you can set system prop jira.dev.mode: true. What actual script error do you get in IE, if any?

"project = 'Prod XYZ'" use single quotes around the project name if it has spaces

Probably this issue: https://jira.atlassian.com/browse/JRA-37337

Installing plugins clears many caches, which can take a long time to repopulate, particularly with say Oracle. This can happen when you have many custom fields and field configuration schemes, as IIRC it does pretty much the cartestian product of those two things in db queries. Lots of projects with lots of roles is also…

That's more or less the final example on the page I posted, ie: https://scriptrunner.adaptavist.com/latest/jira/behaviours-conversions.html#_dynamically_changing_the_picker_query

This is pretty much exactly what select list conversions are for. Set up rest endpoints to get those bits and pieces, and a behaviour to convert text fields to pickers.

I agree with Nic... you don't have a "view issue screen for a transition". However from a cursory look at your code, you are trying to hide the field value, and not the field. So you should use: saveAsDraft.setHidden(true/false) you don't need to get the form value at all.

JIRA doesn't seem to support "project was" natively. I would maybe have a script field that shows the previous issue keys: com.atlassian.jira.issue.managers.DefaultIssueManager#getPreviousIssueKeysForMovedIssues(issueId) which you could then query on. Not tested though...

With the stack trace you might get some sensible replies.

Oh, upgrade failed is it? Of course, that's an easy one to fix.

What have you tried so far? Should be straightforward. But if you don't provide anything you have tried, it looks like you are asking people to do your work for you.

Whatever transition you define for the parent needs to be valid... Also check that you published the subtask workflow If it is can you set the logging to debug for com.onresolve.jira.groovy and retry, and check the logs.

Just hit this myself - com.atlassian.confluence.user.migration.LdapRepositoryConfigurationMigrator#extractObjectClass requires that the filter be objectClass with a capital C. And there's half an hour I'll never get back.

See http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions and http://confluence.atlassian.com/display/JIRA/Managing+Project+Role+Membership.

I don't see that - which version of confluence? If you use certain characters in the title then you get the pageId, eg colon, semi-colon I think, otherwise you should get a sensible title. Are you using any plugins? Eg scroll versions - not attempting to cast aspersions here, but I know that it supports multiple pages per…

google for "groovy truth" ... if you want to check for null use (est == null)