JamieA Expert

I used the following field code: def modulus = issue.id.mod(4)modulus == 0 ? null : modulus as Double and the sorting worked ok, except it sorted them in the order null, 3, 2, 1. Which is not intuitive to me. If you're getting an error there should be a stack trace... although it might be truncated. Can you find it and…

Which indexer/searcher is the custom field configured with?

Fair point... I suspect that they underestimated the amount of work required to maintain the original calendars. If it happens with other functionality I could get a little miffed.

This is pretty tricky. Although I'm kind of fatigued at the moment so I might be missing something. The problem is that you want to query on the worklog index, but you return results from the issue index. Perhaps you can use the above query with another query that uses childrenOf ("your jql") to find issues that have no…

what version did you upgrade from? Script Runner executes the transition as the current user, it has done so for a long time IIRC, so if the user is not in Automation User role then it won't succeed.

Not really. The same issue happens for the "fields required" validator in jira suite utilities. The behaviours plugin can read the requiredness of fields and put the asterisk in with javascript, but overkill for your purpose.

cfValues['System'] || cfValues['Area'] should do it

Hrm, no need to pay for a plugin to do that: http://blogs.onresolve.com/?p=123 ;-) AAC already has a suggestions feature... hasn't helped me but then I pretty much know what is here already!

Doesn't that just bring us back to better search? Not sure this is a job for Herc.

From that blog post, I'd say the problems are equally accidental dupes and borderline dupes. The suggestion of dealing with them is appropriate tagging. AAC does not have enough well delineated tags, and the users don't use them well either... maybe there is scope for improvement in that area.

Hercules mostly works off log files which is a lot easier than parsing natural language, because there are a finite number of log messages that it searches for. Sometimes people post a stack trace so that could work, but not in the examples Nic gave. I say just improve search and let the community decide what is the best…

Can you try this: import com.atlassian.jira.user.ApplicationUserscurrentUser == ApplicationUsers.from(issue?.getReporter() as User) I'm surprised this isn't affecting more people...

Yes, 2) can be done with a standalone install. A standalone install is just a preconfigured tomcat with the web app exploded. Unfortunately there aren't easy options, particularly if you want to keep old urls working. The important thing is to get it right when you first set it up, but of course people don't.

OK... the link above gives you your options.

You need to have a context path for each one, rather than /. It's the same problem as described here: http://confluence.atlassian.com/display/JIRAKB/User+is+Logged+Out+of+JIRA+after+Confluence+Login I'm assuming the server name is the same but the port is different?

"underlyingIssue" is bound in the scripts which is an Issue instance... your way will work fine but make sure you handle the Create case, where issue will be null.

You might need to change the script a bit, see https://confluence.atlassian.com/display/JIRACOM/Automating+JIRA+operations+via+wget#AutomatingJIRAoperationsviawget-BypassingXSRFprotection

Have you set the proxyHost and proxyPort in the server.xml? What is the stack trace in the server logs?

I have a "remember" cookie with a 24 hour expiration and I'm not prompted to login... I don't remember setting that up specifically. Probably there is somewhere you can increase the expiration.

You'd need to set up some form of SSO, for instance using Crowd although that is by no means the only answer. JIRA does not retain your password so could not pass it to Fisheye, and they do not share session authentication cookies (which is where Crowd would come in).

Hrm, I can reproduce that. Must be a classloader issue. When you say "existing behaviour", did this used to work? If so, in which version, of the plugin or JIRA? I raised https://jamieechlin.atlassian.net/browse/GRV-794 to track this.

Yeah, the {repository-plugin} macro is still broken.

I don't really understand the question. The way I read it oneOfTheOptionsThatRequiresMandatoryValueInOtherCF was one of the options.

You could do as Marten said but easier would be: ['ticketCanBeCreated', 'oneOfTheOptionsThatRequiresMandatoryValueInOtherCF'].contains(cfValues['selectListCF'].value) Don't know use *.value unless it's a multiselect.

Things going in the right panels is implemented in SR 3.

it.toString == "Resuelto"|| "Cancelado" That's not valid, or won't do you want anyway. Use: it.toString in ["Resuelto"<span>, </span>"Cancelado"] What version of the plugin and jira are you using?

Not tested, but try: ! ("No-QA" in issue.labels*.label) Try in the condition tester first.

This function is also available in script runner - https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner Admin -> Built-in Scripts -> Impersonate another user.

MSDN is at https://docs.atlassian.com/jira/latest/

In Script Console you won't have an "eventIssue" defined. To get a single issue use: import com.atlassian.jira.component.ComponentAccessordef issueManager = ComponentAccessor.getIssueManager()def issue = issueManager.getIssueObject("ABC-2")if (issue.isSubTask()) { def parent = issue.parentObject // ...}