JamieA Expert

For complicated stuff like this, we need to break it down into parts and make sure all the parts are working before assembling the whole. You said: > I've setup a "customer email listener "and also "Fast-track transition an issue". Can we do just one of those things and verify that it works, then we can move to the next…

issueFunction in linkedIssuesOf('filter = "JK"') and issuetype = "Bug"?

The second argument is optional, if omitted it will show issues linked with any link type.

It's just a type-checking warning, you can ignore it. There is not enough information for it to work out if the code is correct. Your first example is correct for single select, the last one for multiselects. Or are you saying you want to apply this condition on workflows where Region could be any of those cf types?

You could use a validator on the subtask workflow... and/or a behaviour on the subtask type that shows a big red message saying "stop trying this, you won't be able to commit".

Like: if (1) { return true}else { return false} am I missing someting? The return keyword is actually optional for the last statement executed, but you can put it in for clarity.

It's better to use Groovy Truth than comparisons with null. So to check if it has a value: if (cfValues['FieldA']) ... to check if it doesn't have a value: if (! cfValues['FieldA']) ... You don't need to write it in one line, if you hit enter the text box will expand. Seems to be a common misconception that it must be a…

You could use the expression function in script runner. One of the examples in the docs deals with %ages. However that is just for searching for issues. For reporting, I would imagine there is a plugin already that displays something like this. Otherwise a calculated field is a good option.

I don't understand this:this.passesCondition=passesConditionreturn [:];Just do:return passesCondition

I don't know, maybe I removed componentManager from the binding as it's deprecated. The quick fix is to add import com.atlassian.jira.component.ComponentAccessor and replace cfm = componentManager.getCustomFieldManager() with cfm = ComponentAccessor.getCustomFieldManager()

Also try https://studio.plugins.atlassian.com/wiki/display/GRV/Escalation%20Service if jelly seems overly complex.

Yeah there will be but I can't say exactly when. I'm pretty confident that the current version will not work in jira 6 because of the renamable user changes.

Yes, the type of the field is not irrelevant here. You need to set it to a collection of User objects, or ApplicationUser, can't remember which.

If you just the right label, the right people will see this... that's generally more effective than sending me mail. Using the built example worked for me: def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'TextFieldB'}issue.setCustomFieldValue(cf, 'my value') but that's for a text field. What type…

You should get the people that mange the security thing to whitelist jira if it's internal.

Apache or nginx or similar... There are a lot of advantages to setting up Apache. Of course, you get rid of the ugly port numbers, but also you can hold connections at apache until tomcat is ready for them. Also, you can do cool things like url rewriting, for instance I rewrite the avatar urls so we get a common set of…

A screenshot of the configuration would be helpful. If it worked for other selects, perhaps you have just not mapped the behaviour to this project (and/or issuetype)? If you don't want to share a screenshot publicly feel free to create a support ticket at https://productsupport.adaptavist.com/servicedesk/customer/portal/2

I saw your bug report but I ignored it thus far because it contained too much code. Can you reproduce the problem just using that code snippet above? Because the code you posted in your bug report had a lot of conditionals, and you said it worked sometimes... so I thought the problem was in your code. Nothing in computing…

This is fixed in the latest version, https://jamieechlin.atlassian.net/browse/GRV-753

> BTW: Is there any kind of "Loop protection" implemented in Script-Runner? No - it's on you. If you update an issue in an Issue Updated listener just don't dispatch an event, or dispatch only if you know what you're doing. And test all paths through your code. I think I understand what you're saying. You probably want to…

Cedric has put this better than I could myself. Sorry I have not been chipping in, I am having a little break from AAC as I have too much other non-work work for a few weeks. I totally agree that writing javascript back into the helptext is not very structured, and is likely to lead to something hard to debug/maintain. I…

From your question you are trying to insert into a table not governed by jira, which should be fine. From the error message - "Cannot load from mysql.proc" it just looks like it's failing to load or parse the stored proc. But yes in principle it's fine, at a previous place I created one one the role actor tables... can't…

Hi Dieter... It's necessarily dropped, it still exists at https://marketplace.atlassian.com/plugins/plugin.jviz/server/overview . I asked that users donate money to a charity for use but I don't think that ever happened. It's true that it hasn't been updated for JIRA 7 though. I see value in it too but I'd probably do it…

time tracking stuff is not supported well in behaviours at the moment...

IIRC it's getFieldById("timetracking")

Use ComponentAccessor.getComponent(...) but otherwise yes that's the problem. You can tell by: No signature of method: static com.atlassian.jira.security.roles.ProjectRoleManager.getProjectRole()

Beware if the action contains important information... AFAIK that only hides the link, not access to the url if you know it. Best thing is to check your criteria in doValidate method as well... IIRC.

You don't want a script field, you want a post-function. There's no such thing as an invisible script field - script fields are not present on screens where you can edit, eg create issue.

You want Admin -> Script Event Handlers, new Custom event handler. Event to listen for is: PullRequestOpenRequestedEvent Code (put in file or enter directly): import com.atlassian.bitbucket.event.pull.PullRequestOpenRequestedEventdef event = event as PullRequestOpenRequestedEventdef from =…

worked fine for me, can you attach a screenshot of the configuration, and include version information.