JamieA Expert

For create screen I think you'd use behaviours (part of script runner), or roll your own javascript.

The approach described here and in the linked gist should work for any calculated field: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted%20Fields#ScriptedFields-DisplayingScriptFieldsinTransitionScreens

Yes, but use CustomFieldManager to get the CF value from the issue. 

It can't really know what it's done, in order to undo it all when you change projects. The user may have made further edits and would not expect it to be wiped out. In my experience, most end-users, most of the time, generally create issues in one project.

It sounds like your indexing is broken for some reason... this functionality is not going to help you if the issues are already broken. I've taken it you've tried restarting and doing a full reindex?

It can be configured as a listener... Admin -> Script Listeners -> Send custom email, and select the Issue Commented event.

I can only suggest the send custom email built-in script from the script runner plugin, which has the option of sending all attachments, or attachments added this transition or event. However, unless you go to a lot of trouble, the email notifications are going to look different. Failing that you could take the code and…

I think it should just issue.description = 'Some Text.\nNext line of text."

I think unfortunately you will need the FQCN, ie: com.atlassian.jira.component.ComponentAccessor

It doesn't help if you need the contexts to have different types, eg short text and long text. In that case you have to go the "punctuation trick" route, with two fields.

you want: if (! workflowTransitionUtil.validate().hasAnyErrors()) { // ... all good} .validate() returns an error collection that you can look at to see what the problem is.

It's a pain to query on the sprint, you need to work out the sprint ID - see https://jira.atlassian.com/browse/GHS-4949. Also see my comment for a possible solution.

Nice job... minor thing, I'm not sure that's the best way to get the attachment file. If the issue has been moved that may not work IIRC.

You have full control over the Mail object, so you should be able to do it. The closest thing in the docs is https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_adding_generated_attachments. In the linked SO.com answer it says outlook ignores the ICS attachment. So you need to create and add a new mail…

Be sure all your repos are structured in the way that fisheye likes: https://answers.atlassian.com/questions/19281/how-can-i-reduce-the-size-of-the-fisheye-indexes . I ended up writing something to automatically generate the exclusions. 30Gb repos doesn't really tell us anything useful. It could be binary files, in which…

FWIW - anything other than file:// access is pretty much a non-starter for real life svn repos.

Bah, accidentally deleted my comment. Be sure that all your repos are structured in the way it likes: https://answers.atlassian.com/questions/19281/how-can-i-reduce-the-size-of-the-fisheye-indexes I ended up writing something that automatically generates the exclusion rules. 30Gb repos doesn't tell us much - if it's binary…

I would try what Justin suggests. I think the "licence error" is a general catch-all error message. In addition, when you try to enable it a stack trace should be logged - can you post that?

Isn't this a confluence not a jira problem? Anyway, you can query the attachments table for the ID in the url.

See https://jamieechlin.atlassian.net/browse/GRV-42

You can trap permissions being changed on a repository... if it's a personal repo, prevent the permissions change. But, I agree with Tim, mostly. It depends if you want to prevent inadvertent source leaks or deliberate. If it's the latter, as Tim says, it's just trivial additional step. I don't really agree that Stash is…

I don't think that's a problem. What I would look for is things like connecting to external databases etc... only way of telling though is with a profiler.

It depends what you do with them. It's really impossible to say much more without knowing what your code does. You could time a full reindex with and without the script fields... the time difference will give you a very basic idea of the amount of additional work they are doing. But in terms of ability to blow yourself up,…

You just want to add "count(*) as Kount", group by title, filesize, and "having kount > 0"

I would use ranking in greenhopper. Otherwise, you could write a calculated custom field.

Also https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-workLogged(worklogquery) (free plugin) for download instances.

Also https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-workLogged(worklogquery) (free plugin) for download instances.

The extra GH metadata such as start and end date and hierarchy was implemented before it was one company... it does seem to have taken a long time to align some of this stuff with core jira concepts.

Firstly use the correct labels for your question so you get attention from the right people. Read - https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-SetIssueSecurity - it tells you where to position the function. Second, check the log file.

> Jira simply tries to bind to the LDAP with the credentials the user provided on the login page. If that succeeds, the user is authenticated. If not, the user is rejected. That's not quite true. JIRA will bind to LDAP using the bind user you give as a param, search for the user using the uid=<login> filter, or whatever…