JamieA Expert

This is not making any sense. You can't set the value of a scripted field. You modify the script field code so that it returns a value based on the two select lists.

In private emails you said that all fields are select lists. To set a select list value you will need to send the option ID, which is like 12345. This is not ideal but this is how it works right now. Maybe in future there will be a setValue() method, like the getValue() method, which has a bit more smarts.

What type of field is MyFieldOutput? Add some logging, eg log.warn ("F1: " + F1) log.warn ("F2: " + F2) and look in the jira log after activating the bejaviour. Also please don't start your variables with an upper case char.

EBS_ Request There seems to be a space after the underscore.

Can you change it to: assert ['EBS_ALERT', 'EBS_Request'].contains(issue.issueType?.name) And preview with one of those issue types. This should produce an exception which will give enough information to work out what it thinks the issue's name is. If it's not clear from that post back here with the top part of the…

Relates is tricky because the destinationObject might be the current issue. Try adding the relates link the other way as well to see if that's the problem.

linkedIssue.getIssueType() returns an issue type not a string. So you would want:linkedIssue.issueType.name == "Bug"there may be other problems too.

I fixed the formatting. Can you post a stack trace or something, or what the actual result is compared to the expected.

This is very similar to this example: https://scriptrunner.adaptavist.com/latest/jira/recipes/scriptfields/workRemainingInLinkedIssues.html - did you check that out? Also it would help readability if the code was formatted properly.

mm/dd/yyyy Lower-case m is minute in hour, you want MM, not mm.

I put wget/curl in the same basket as web crawlers. You could save yourself some money and just run p4web in guest mode. But, my point stands, if you are concerned about people seeing code they should not, you should only give access to fisheye to those people that have read access to everything in p4, and also see…

Why script a web crawler when you could just check out the repository? I think the idea is you only give access to people who have access to the source repo... in this respect fisheye is very weak, because it doesn't have the capability to read the permissions of your source repo, be that subversion or perforce or…

groovy script ;-)

Or you could turn it into a proper plugin with by changing scoped-web-resource to web-resource in the plugin.xml (not tested).

Why don't you just take the javascript in the single file in that plugin, wrap it in script tags and put it in your announcement banner? It's the same solution as I wrote here: https://answers.atlassian.com/questions/12799/usability-of-minor-change-checkbox

Presumably you're using a custom authenticator plugin? If so you will need to modify that.

You can use ScriptRunner to "become" another user. If you want to do it in bulk or automatically you can use the API. Not sure what your preference is... if the users are already in your LDAP directory you probably already have location info, from which you can get timezone info.

You don't say if it's jira4 or jira5... what should work for both is: AJS.$("#attachment_box").live("change", function () {alert("blah")}) (within the document ready handler). To ensure this javascript gets on every page you need a plugin with a webresource context of jira.general. Or you can just put it in the…

You could modify the "JIRA News" gadget... or find some other OpenSocial RSS feed gadget.

I used the following additional code in an escalation service, with no action, and it worked fine: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.ModifiedValueimport com.atlassian.jira.issue.index.IssueIndexingServiceimport com.atlassian.jira.issue.util.DefaultIssueChangeHolderdef…

what JIRA version and plugin version?

So the option is there. In your original post you used targetField.updateValue, but later you mentioned issue.setCustomFieldValue. If you are not doing a transition, you need to use the former method (or IssueService.updateIssue).

Vijar... your script looks OK to me... can you put the option in a variable called option and then log.warn (option), and see what you have in your logs. You could use: find { it.value == 'E1' }) rather than toString(), but it should give the same results. Also check your E1 doesn't have any whitespace after the string.

Sounds like you need ranking. There's nothing stopping you ranking a low-pri higher than a high-pri though, but personally I don't think that matters.

Velocity is just not flexible enough to handle that syntax. You can do it by using a ContextProvider to make a variable called $email available in the velocity context. You can see how to do that in this example: https://answers.atlassian.com/questions/43888344

Wow... that's a pretty serious issue.

I think you need to use the send email listener with a condition that the field has changed, and is the value you want to check for. Using the behaviours plugin is all well and good, but it will send the mail as soon as the value is changed, and before the issue is even saved. I know they wanted it sent "as soon as" but…

Go on then, give me a vote up, I just gave you one!

A calculated field of some type is easy too, only disadvantage is that you need to do a full reindex, and it wastes a bit of storage index space, compared to writing your own jql function.

Several different options you could use. You could create your own jql function that does this using script runner. Then you could run a query like: issueFunction in isStakeholder() and project = "Some Project" It's not too hard, the code is below. You just paste it in, give your function a description, and that should be…