JamieA Expert

Well that's why I asked what character you were thinking of... it's so unlikely as to be a hypothetical question only.

UTF-8 is an encoding, not a character set. Do you mean input a character not in the Unicode character set? If so, which one?

I don't think working off logs is the best way to do this... you're better off querying the database directly: ChangeItem, ChangeGroup tables... they will have all the information you'd get from the logs.

That's not script runner, it's the workflow report plugin. Looks lik it's misconfigured, but, you probably should just uninstall it as it's pretty much obsolete.

lastComment is just the comment body. comments.last().authorKeyshould give you the username, but make sure there are actually comments, otherwise that will throw an null pointer ex.

Matt - your way is fine, but the last comment is placed in the binding, so you can just do as in the example in the docs: https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Sendacustomemail <% if (lastComment) out << "Last comment: " << lastComment%>

Agreed. Have some points.

I didn't want to leave this question hanging... so, after using 4.4+ for a while, I really really like the admin navigation. It's a massive improvement once you realise it's there. Then it becomes automatic, and using previous versions is painful. I still think it's a pain creating a project now, fortunately we have or are…

Works for me, although for quite a few screens the first form field infuriatingly grabs focus, and the GG goes there.

And yeah sorry I got my own question wrong, I meant 4.4. Up to 4.4 I could understand what was going on.

No I'm not ready to inflict it yet on our support team...not until I can explain why everything's 5 times clickier.

If you've written your own code can you attach it?I would say you just want the most recent attachment.

I'm not sure what you mean really. When you say pop-up windows I think you are talking about a workflow transition? > Right now emails are sending, what ever file is latest but we need only when file added in pop-up windows. How are you currently sending an email including the attachment? If you are using the "send email"…

the mouse over hover should be disabled. All browsers or one in particular?

What version are you using, an issue like this was fixed recently.

Please use the correct tags.

I don't think it's possible either, but you could have a post-receive hook in gitolite that pushes to Stash. Probably easiest just to make the gitolite one readonly, or a add a pre-receive hook with a message to update the remote... people will get the message.

There is a setContent(String) method - have you tried that? In fact I can see content:"" in the hash you are passing - just add some content to that string.

Brilliant, thanks. The change I made for the snapshot is in the version released last night, 3.0.2.

Great, thanks. Did you try with the snapshot version, and that then gave you the clue about the space? Or it didn't warn you about that? I raised https://jamieechlin.atlassian.net/browse/GRV-485for the issue with spaces, but have not tried to reproduce yet.

Robert, can you install the snapshot of the next release version from https://jamieechlin.atlassian.net/wiki/pages/viewpageattachments.action?pageId=33619976 This should tell you why the function is failing to load.

First of all it's good that you are trying a stubbed class. It's no good that the compilation error is not shown, I raised https://jamieechlin.atlassian.net/browse/GRV-476. I tried the class you posted and it compiled and was added. Have you tried with that exact class? Is it in the correct directory under your script…

Bob... how do you specify the mapping from old states to new states, in the case where the workflows have different lists of statuses? Or if you can't do the mapping, what default is used?

You need to uninstall the plugin first before installing the older version, IIRC.

yeah, plus look at the built-in scripts, plus lots of code here in AAC.

Or script runner... there is loads of sample code that does what you want.

You may have used every possible combination, but you've used it in the wrong place. If you like, send a screenshot when using the "simple scripted condition". Alternatively you could write your own plugin if that's easier.

OK then instead of: issue.resolutionObject, use: issue.statusObject.name == "Closed"

To be honest, none of those make any sense. If you want that all subtasks should be resolved except those of type "Testsub" - and that needs to be the issue type, not the summary or something, you could use: issue.subTaskObjects.findAll{it.issueTypeObject.name != "Testsub"}.every{issue.resolutionObject}

The condition tester with asserts can help you get the code right... https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-PowerAssertions