JamieA Expert

AFAIK the changes required to convert a speakeasy extension to a proper plugin are pretty small. So if you want it available to everyone, sounds like you should convert it to a full-fledged plugin.

Now I'm really confused. What you've posted there is about operator precedence, and yes generally AND is higher than OR. But that's nothing to do with JQL, which the docs say is parsed L to R. What is this code exactly?

> and presummably changes the results/meaning of the query But does it? As a quick check you can just see if the same number of issues are returned for both queries. If they are different, looks like https://jira.atlassian.com/browse/JRA-39107.

Agree with Nic... also question whether a marketing/branding play really qualifies as important information.

Hello Agile!!! Now GTFO. Thank you thank you thank you for adding the cookie.

1) As Manse says. This should be made much clearer in the UI imho. 2) It will only do that for users in the internal directory. From the user browser you can see what directory any user is in. BTW, feel free to give some upvotes/ticks for helpful comments.

Set it up first on 4.1 using the osuser.xml file. When upgrading, copy the osuser.xml file to the new installation directory before starting the upgrade. Then on upgrading, an upgrade task will create a new internal directory for delegated ldap auth, and migrate all the users from the internal dir to the delegated dir. I'm…

It's in the plugin, you can add the plugin jar to your pom.

Yeah just drop the jira database and recreate it.

Yep, that makes sense. In that case ignore my answer above.

It depends on the permission scheme. Normally, the project role Administrators is the correct option here. Check the permission scheme for the project - possibly someone has modified the default permission scheme (bad idea). Also it doesn't look like you're in the project admin section from that screenshot...

You can also insert menu items using the examples here: https://scriptrunner.adaptavist.com/latest/stash/CustomisingUI.html. They are for Stash but it's the same principal for JIRA, although it's probably a bit more involved than you'd want if you haven't done anything like this before.

I think you're talking about changing the workflow depending on the value of a custom field? (And not diagrams per se.) You can switch the issue type in a post-function depending on the value of the CF, and this other issue type could have a different WF. But, the code to do an issue move is bit difficult...

It should be: issue.resolutionObject.name != 'Training Delivered' || cfValues['GP Code checked'] Which means, if it IS traning delivered, that checkbox must have a value. It;s kind of inverted... lots of examples…

Can you describe what you want to achieve.

Sounds like a bug then - please could you create an issue at https://jamieechlin.atlassian.net/browse/GRV.

There is a key field on user which is the original username of the user, in lower-case, since I think 6.1. I don't know what is actually indexed, but I would assume it's the current user name. If that email address is actually the user name, then Nalin please let us know.

Actually it is probably the key, and the search function converts user name to key. I'm not 100% sure this jql function works with renamed users - there are a number of bugs related to named users that I need to address.

I don't see any getProjectCategies method here: http://docs.atlassian.com/jira/4.4/com/atlassian/jira/ComponentManager.html ComponentManager.getInstance().getProjectManager().getProjectCategories() should do what you want.

The above (commercial) or script runner (free). After installing go to Admin -> Builtin scripts -> Impersonate another user.

There is an "Assign to role member" built-in script in the plugin since a few months ago... did you try to use that?

There was a question about image annotations recently, I suggested a jquery plugin. I can't find it now and I'm afraid you can't search this site.

You might want to take a look at this confluence plugin: https://plugins.atlassian.com/plugin/details/37075 I have not used it, I don't know how well it works when annotating images for instance. I like the idea of a number of layers that you can quickly flick through to see the evolution and the comments, but AFAIK there…

Put a validator that prevents creation. To stop people entering the form fields do a big velocity-processed custom field for edit that says "stop, you won't be able to save". Or write some javascript that removes the type from the create subtask screen.

Or look at com.atlassian.sal.api.scheduling.PluginScheduler, plus a component module which can install the service if it's not present on plugin startup.

It will be fine if you write the condition safely. It should not cause other post-functions to fail anyway IIRC. You can always put it in try/catch...

So you just need to follow the link from child to parent - I'm not sure which bit you're stuck with, you seem to have most of the relevant code.

@Chander Inguva - you're not waiting, we answered it. @Josh Costella - when do you want this to happen? As we said to Chander, it's not possible to trigger it based on a link being added, but you could trigger it on state change or something.

It's a bug in JSD, it fails to show validation errors. Maybe: https://jira.atlassian.com/browse/JSD-1638

Best thing would be to add a groups custom field to the issue and use that in the notif scheme. Then you will need to deal with setting the custom field to the groups according to whatever criteria you need, which is easily done in a script or plugin.