JamieA Expert

When I saw Marek's picture above, I had exactly the same thought as Radu. What if you need to change one of the constant values, eg 3000. Painful.

Yeah, I like it... nice and simple.

Thanks Beth that is also interesting. I'll check out Jive, I've also been looking at Kindling.

interesting, thanks.

I can't make much of a comment, but thanks for following up with the outcomes.

;-) no problem. That particular thing of sending mail to a recip provided by a scripted field has not been tested that much, LMK if you have any problems.

Hi Francis, The version released about 10 minutes ago (2.1.11) is less fussy about the field types. So long as .toString() on the field value looks like an email address, or a comma-delimited list of email addresses, it should work.

Brent, this should be a new question. Select lists have Option values, to get the string value you want: Account Name: $cfValues['Account Name']?.value

It would need to extend UserCFType, or I'd need to cater for it specifically.

In the to section, you should just enter the ID of the custom field, eg customfield_9999. If it's the right type, for instance a User custom field, then it will be handled. Your code is correct for the template, but that's processed different. The to list is just a list of fields, rather than a groovy program that is…

Hi Jobin. They do not. One of the plugins Lokesh is referring to was written by me. I can't remember how in the plugin.xml to specify that various renderers are allowed. In the list of renderable fields it does not include calculated custom field, which is what this is. So I guess that means it's not possible?

Jayant: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted%20JQL%20Functions. As Jobin said, both plugins are available from marketplace.atlassian.com.

Also ScriptRunner.

More recent versions disable inline edit for those fields where a behaviour is applied. Inline edit can't sensibly be used when you're trying to validate multiple fields in conjunction with each other, so it just disables it.

The "did you mean" index currently only supports English, that is, the indexing Language must be set to English for "did you mean" even to be available. Therefore I'm not sure how this could possibly work for suggesting hits to German content. I would vote for https://jira.atlassian.com/browse/CONF-14768.

Maybe I will add some form of auditing, perhaps that would suffice.

Yeah. Nic is correct in that I looked at it. My justification for not doing it was broadly that, if you have an admin who wants to intentionally abuse that functionality, and you disable it from them, they could also equally abuse that privilege by using the workflow functions, eg the "scripted condition". I could prevent…

@Barthélémy von Haller - bear with me, I will test this again.

Yes, you will need to set the resolution.

No worries, I created a bug: https://studio.plugins.atlassian.com/browse/GRV-110

Correction. I did read your question, but you changed it afterwards.

I didn't fully read your question properly. 1) your condition is wrong, which is why it works with an empty condition. 2) That page refresh thing - I have seen that recently and still battling with it. Basically the transaction happens in a separate thread to work around the jira 4.4.3 bug, but it has the side effect of…

Good point. From the docs: Place this as the last post-function, or at least after the Fire Event function. If you don't do this, it won't work.

It's tricky doing the transition on the creation step, although it is tested and should work. JIRA 4.4.3 has a bug that could cause problems. What version of jira are you using? Your condition is wrong for radio buttons, it should be (IIRC): issue.cfValues['Immediate resolution'].value == 'Yes' But use the condition tester…

There's no screenshot. They must be in production somehow... try doing a "find" in the jira home directory and grepping for a bit of the plugin name.

> One of the other features I would like is to be able to filter my rapidboard based on that value That *will* work if you utilise the number searcher. But then of course you won't be able to use workaround for sorting that you have.

A bug report containing just a summary and a link to this would be helpful.

The template just governs how it's displayed, not the sort. I'm afraid I have hard-coded it to compare as Strings. To deal with this I need to give the user the option to "overload" that, but then you're moving away from a "simple scripted field" that is supposed to be easy to use for non-programmers into a nightmare of a…

You can only remove UI items if they are shipped in the plugin as a <web-item>, <web-section> etc etc. Unfortunately JIRA Agile does not play the game. You can do it by injecting some javascript using Script Fragments -> Install web resource - but it's not as easy. The context is "gh-rapid". Hide the flag using:…

If it works in the preview but the actual email doesn't work, this is normally caused by using the dollar character. Try to use this: <% out << issue.assignee?.displayName %>rather than${issue.assignee.displayName}For instance at the beginning where you include the issue type.Can you also try with a ScriptRunner script…