JamieA Expert

You mention in your tags script runner and JJupin, but neither plugin is available in OD. You can do this without using a plugin by setting a condition on your Ready transition that checks the required fields are filled, and then use the "auto" property on the transition - more info here:…

You could use the Clone Issue function from the script runner plugin, this lets you specify a target project and issue type without writing any code.

has the problem user been renamed? Older versions had a problem with renamed users. You could check with the user key is the same as the username in the database...

and check the logs...

Is that user logged in? What happens if they run that query as a jql query in the UI?

You can use this post-function to do this: https://gist.github.com/jamieechlin/8240692 Obviously various params would be replaced by custom field values etc. You could copy the source, but I don't really recommend it - multiple maintenance problems.

Yes, that's what I said in my original response. I don't recognise it.

I can't really see that screenshot properly but I don't recognise it as part of ScriptRunner. Can you check your logs, and create a support ticket at productsupport.adaptavist.com/servicedesk/customer/portal/2.

Typically it does, but not always (which is a bug imho). If you are running a query in the issue nav, it will always be called first, however I have seen occassions where it doesn't, for instance when starting up jira and then going to the issue nav, the last query that user ran is run. My workaround is to extract any…

Code. Example: https://studio.plugins.atlassian.com/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Updateblockingissues This will add a comment to issues linked when the issue is resolved. Adding the comment sends a notification.

Not OOTB, but this plugin is available: https://plugins.atlassian.com/plugin/details/30365 .

You could just delete and re-add the one repo from the repositories page. However yes it does not really handle this situation.... it's not really acceptable to have to reindex the whole svn repo just to handle this. Fisheye is slightly better in this regard but it's still not automatic.

Did not the script in my answer work?

You can only use cfValues in the "Simple Scripted Validator". I guess you are not using that. It doesn't seem like the best way anyway, you need to keep the strings in sync. Here is a custom validator that checks that all possible options are checked: import com.atlassian.jira.component.ComponentAccessorimport…

Reasonably, other than you're not returning anything. I think you should be able to use linkedIssuesOf to get all PBIs or whatever, and then do the version comparison...

You want me to write it for you? That's not going to happen. Just make a start and ask specific questions when you get stuck.

So there is a relationship between PBI and SAR, perhaps through an issue link? At its simplest, this just involves querying for PBIs, finding their linked SAR, and comparing the two fields. If there are multiple fix versions, you should find out what the client actually wants to happen. I would work out all the cases and…

I'm sure you can but what is your requirement exactly. Can you give an example? It's not at all clear.

They can be inferred usually, eg in issue.subtasks.collect {it.summary } but not in def c = { it.summary }issue.subtasks.collect(c)

When you say "assembled using make" what does that mean? Can you slim it down to a representative sample?

This is a good answer for you: https://answers.atlassian.com/questions/2/what-reporting-capability-is-available-from-jira?page=1#16167

Sounds about right to me. The good news is that this is fixed from 5.0 onwards. https://jira.atlassian.com/browse/JRA-25122

If you want to do this for your entire jira instance, the easiest way is just to disable the plugin module that provides that link. Go to Plugins -> Issue Operations Plugin, find the module "View Issue Ops Bar Convert to Sub-Task Link", then disable that module alone.

great... there are a couple of issues you might run into. Look out for an update soon.

John's answer doesn't work for planned sprints, and also the argument should be a numeric ID that is not that easy to find. See my comment here for a possible workaround. PS Just adding support for mysql now, other dbs should work ok.

Filter name is not unique, and attempt to do programmatic stuff in jelly seems painful to the point of wondering why you wouldn't use groovy or another scripting language, but anyway, I'd stick with the ID. If you want to do it you need com.atlassian.jira.issue.search.SearchRequestManager#getSearchRequestById(User user,…

Try a grid plugin.

That's odd... it only gives me a non-null value when I use the following way of getting a custom field value. No idea why: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.MutableIssuedef customFieldManager = ComponentAccessor.getCustomFieldManager()MutableIssue issue = issuedef cf =…

What (plugin or script) are you using to copy the field?

Yes, they are velocity templates. I tried to answer your question here: https://scriptrunner.adaptavist.com/latest/jira/scripted-fields.html#comment-2928282368