JamieA Expert

The importers plugin has a hard-coded list of field types that it's prepared to import from: https://ecosystem.atlassian.net/browse/JIM-787 You could modify the source of the jira importers plugin. If you want to do that I can find more details.

In addition to what the two other answers already say, you can use Behaviours for dynamically displaying a field value based on other field values: https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html

You probably should start with https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/select-list-other.html, and you use setFormValue to set the field. It's easier just to do this with a listener though.

The official quote is 200k - 300k, but it's never backed up by any explanation of where the bottleneck is. You should take it with a pinch of salt, many sites including mine have way more than that, although you need to tune often. IMHO you won't get any benefit from switching to oracle, probably the opposite.

Old post but... it's quite common that the default is just a null value, which maps to eg the default issue type scheme. Changing it would be relatively painful. More easy to just build your own "new project" functionality that creates the project with the defaults that you want. More easy, but probably still difficult…

Yes, it has a copy project built-in function.

Is this self-hosted jira? If so are you sure they're getting stripped - possibly they are just getting executed too early. Can you paste an example of one of your scripts? https://developer.atlassian.com/display/JIRADEV/Preparing+for+JIRA+5.1#PreparingforJIRA5.1-CustomFieldsthatuseCSSorJavaScriptWebResources

Mick's comments makes a lot of sense to me. I haven't tried this but you should be able to block clone/pull/fetch etc, in fact all git interactions, using an SCM request check module: https://developer.atlassian.com/stash/docs/latest/reference/plugin-module-types/scm-request-check.html So you could block all access to a…

There is code that handles this for subtasks already written, but bear in mind that ticket in project B may have a completely different workflow, it may not have a similar valid action for the current step etc etc. What do you think should happen in that case?

OK, sorry... in that case ignore me. Was just a shot in the dark.

Not sure, but are you using an old version of the behaviours plugin? I'm curious because it used to do that red outline which I think I see on your screenshots. There is no known issue along these line, but perhaps you have a behaviour that clears the help text (as I refer to it). If so you should disable the plugin and…

You need to go through them one by one, looking at the stacktrace and other messages in the log when you try to enable them. Uninstalling is unlikely to make any difference. Feel free to post the errors here.

some changes were made to that, can you try the most recent version?

if you need help with that, can you provide the version of ScriptRunner pls

You have to check it out from github, build it, install it. I had to do this too, it worked fine for me.

The username/password on line 15 looks odd. It's this that is throwing: https://bitbucket.org/cmiller_atlassian/confluence-json-rpc-plugin/annotate/31356045ef00/atlassian-voorhees/src/main/java/com/atlassian/voorhees/JsonRpcHandler.java#line-62 If it was me I'd probably install jira locally and attach the debugger, and see…

Out of interest why are you masquerading as firefox? Also httpbuilder should add the content-type header automatically, maybe the server is getting confused by having two? I would recommend proxying through fiddler to see exactly what you are sending, although it can be a pain with SSL. You have to fiddle around with the…

The issueHistory function just shows issues the current user has recently looked at, and will only show a maximum of 30 issues. It's not what you want. You would need the WAS operator but it's not supported for links AFAIK. I think you will need to write some kind of script that parses the history items using the REST…

You have singularly failed to understand the point of this web site.

cfValues['Doc Impact']*.value.contains('Yes')

issue.projectObject.key in ["ABC", "DEF"] or ! (issue.projectObject.key in ["ABC", "DEF"]) depending on what you want.

I don't understand where Due Date comes in to this. Can you attach a screenshot? If you've put the error against Due Date it will go against that field, but if that field is not in the validator it has nothing to do with whether the condition passes. Is your objective to make the due date required depending on some other…

Use brackets. Use the condition tester with asserts, that should make it clear. https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-ConditionTester<br< a="">>https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-PowerAssertions

For multiple approvals my general advice would be to create a new sub-task Approval issue type with a simple workflow (open->approved, open->rejected etc). Then create as many subtasks of type Approval as you need. There are plenty of plugins that can help here with either creating a bunch of subtasks automatically after a…

You can press F11 to enable full-screen editing... but yes, it needs to be resizable, and probably be wider by default.

I had to pay UK customs GBP30 for my swag, although there was quite a lot of it to be fair. @Dieter - let Atlassian know through the swag contact form - they feel you should not have to pay additional charges.

I have to say I really like my original KK design with qr-code... you've got a talented t-shirt designer!

I got my t-shirt, thank you kindly.

Mine too Dennis! Someone mailed me a few months ago but I never received anything. Not to mention the laptop bag!

Make sure you have "delete issue" permissions... normally by being in the administrator role for the relevant project.