JamieA Expert

All true, but this:issue.get("Priority")is only valid with JWME afaik

I think this question is actually about JMWE and not script runner, you might want to change your tags.

sorry - what do you mean by "after modified"?

Don't use the rest API... you can use the java API. Our docs are mostly correct apart from the location of the WorklogAttributeService. I'll check it and get back to you.

our docs are for tempo 7, it won't work with tempo 8. We're working on that.

Yeah. Certain views in fisheye, such as annotated source views, produce pages with grillions of DOM elements. IE does not handle this well at all... Chrome or Firefox are much quicker. Also, I doubt that IE is the default browser for anyone at all in Atlassian... it stands to reason that their apps will work best with the…

You might need to click edit, then you can specify the interval in minutes.

You need to use com.atlassian.jira.issue.changehistory.ChangeHistoryManager. Google on that, you should find some examples.

Oh didn't see the tag. I'd probably knock something up with the remote API for OD then...

Normally you'd modify the space velocity templates to achieve this, although I don't think that's a good idea personally (for reasons discussed in answers before). You could use a plugin that uses javascript to write the rating macro where you need it to appear...

Don't think this is possible right now: https://productsupport.adaptavist.com/browse/SRJIRA-2159

> If your source branch can be 'classified' as 'feature', 'bugfix' or 'hotfix', then the merge conflict resolutionAh, that explains why I could have sworn I'd seen the reverse instructions before. Thanks Michael.

I'm not sure what you have done here. I would uninstall both behaviours and Script Runner. Then install Script Runner 3.0.7. Then you will have the behaviours link in the admin section, and it should be exactly like previously. If not, stop there and let's work through whatever the issue is.

+1 for using the "Anyone" group rather than jira-users - http://blogs.onresolve.com/?p=95. Makes a huge difference.

There is some info on this here: https://studio.plugins.atlassian.com/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-expression%28Subquery%2Cexpression%29 Not applicable to OD though. Timothy is right, but it doesn't take into account the remaining estimate.

By "conditional transition" I read a condition for a transition. It sounds like Nic is reading an automatic transition if a condition is true. If that's what you're after, and by your own answer I don't think it is, take a look at auto-transition. Plugin details on parent page.

Worked fine for me. Can you be more specific about what doesn't work, and include version information.

Script Runner includes worklogged... eg issueFunction in workLogged("after -4w by jbloggs")

Also see http://www.nicholasmuldoon.com/2013/06/using-the-epic-workflow-in-greenhopper/

Duplicate of https://answers.atlassian.com/questions/29753/remaining-time-on-resolved-done

com.atlassian.user.GroupManager#createGroup ...?

Isn't this just clustering? What about changes to metadata... components, projects, versions, or are you only interested in syncing two projects?

Take a look at https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/select-list-other.html. If you want to hide a value just called .setHidden(true). If you still need help can you be more specific about what's not working, include screenshots and the code.

That's available just from /issue - docs: http://docs.atlassian.com/jira/REST/latest/#id2474348

I'm not sure I would go that far, but I have had very irate users complaining to me, and ultimately I have to take the responsibility for not turning it off. The algorithm is not very clever either... before I turned it off I was getting the same recommendations every week, and it was all for content I had actually written.

Did you mean to tag this jira-cloud?Your conditions look ok to me, but what version of JIRA is this?

It would be a fairly simple modification of the script. All the code for that exists in other scripts, so it's a case of combining, and testing. If you don't have much programming experience it's a steep learning cliff. It may be available in other plugins... not sure.

You can find the script in the jar file which you can download from marketplace. It doesn't support renaming users across directories. In the next release I will either fix it or remove it.

This seems like an answer to another question.

No need to be quite so dramatic about it. UTF8 wasn't invented just to screw over Mikel Rodriguez. What template is being used for the field, can you attach a screen cap of the script field config? Can you make a simple script field with the script: "ñ, á, é, í, ó, ú" and see how that renders?