JamieA Expert

I wasn't saying the question didn't make sense, just that allowing a null value in the picker generally does not make sense, that should be handled in a different transition. Although my post was over a year ago. Script runner plugin has a built-in script that can fix this problem:…

You generally need to pass the issue through a workflow function that clears the resolution. For example take a look at the "Reopen" transition in the default jira workflow. Alternatively it can be done programatically. The reason for this is that you generally only show the Resolution field on a screen on a transition…

clearTIme clears the time part on the object you you call it, and returns that, which I eventually worked out from http://stackoverflow.com/questions/6739561/groovy-date-cleartime-question So your original code would modify the issue object in the current thread, but not actually store any changes to the database.

The latest beta version (https://jamieechlin.atlassian.net/wiki/display/GRV/Upgrading+to+3.0) works in stash and confluence as well as jira. But no intention to make it work in fecru...

Hi... I thought this would be an easy task but actually it turned out, not so much. There is much more code here than I would hope an SR user would have to write. Also there are many different ways of doing this, perhaps my way is not the best. It does work, but I feel like I'm missing a trick. The code is…

is there anything in the logs?

I presume you have no listeners that are doing something when that Allgemeines Ereignis event is fired?

Those fast-track functions... do they have mutually exclusive conditions? Setting the comment may not happen if there is not a screen for that transition with comments on it, other answers suggest to use CommentManager to create the comment.

I just edited this answer to include the link, in case of any confusion.

How are you calculating the number of files on disk, using a "find . -type f" ? I presume you're not doing something odd like auto-versioning with subversion, so I think you need to give some examples of files that are on disk but not in the database.

Well - you've made the presumption that there can be orphaned files, and I don't think that's the case.

I think you should check that assumption first, otherwise you're going to cause problems. Better to work out an attachment limit, and see which issues have attachments over that size. select sum(filesize) from FILEATTACHMENT - run that on that on your db - if it's less than the size on disk, allowing for disk block sizes…

A suggestion to accomplish this would be for each project to use their own permission scheme, where the permissions are granted to groups (projectA-devs, projectA-users etc) , and the names of the groups are then assigned appropriate permissions in the scheme. Your workflows would also need to not use role, but use the…

This sounds highly related to this jira issue/question: https://answers.atlassian.com/questions/12956/jira-full-ldap-integration-how-do-you-deal-with-retiring-users. I think Atlassian have somehow missed dealing with this.

updated my answer

Hint: A cascading select is not the right solution. You can use something like the following behaviour, as an initialiser IIRC: import com.atlassian.jira.bc.project.component.ProjectComponentimport com.atlassian.jira.bc.project.component.ProjectComponentManagerimport com.atlassian.jira.component.ComponentAccessorimport…

Yes, adjust. Or remove the condition.

Yes. I meant the the issue by "it". Can you mark my answer as correct, to help other people. By clicking the check/tick mark.

It needs to be assigned to the current user. There is a condition on the default workflow. You can adjust that if necessary.

You can probably just do a cast there: DateUtils.getDurationString(Math.round((timeDiff / 1000) as Double)) Not exactly sure what's going on, but it's obviously having trouble inferring the type for "timeDiff / 1000". It's safe to ignore the type checking…

Go to admin -> Script Fields. If you don't see it there then the CF has been removed. If not it's still there...

Hello... I think you do have some custom code. It's telling you you have a field called Release Week, which uses a script to calculate its value. That's failing.

Somewhere between 6.3 and 6.3.7 jira has changed to throw this exception during stop-the-world reindexing. I don't know what the solution is, as it makes sense that you can't do a search during reindexing. Please could you watch: https://jamieechlin.atlassian.net/browse/GRV-569

I don't think this is related to the OP's question, so I'd create a new question including the field script.

It's your code failing, not mine. Look at the script code for the field "My Field Name". Admin -> Script Fields. Feel free to post the code. But it sounds like you are doing a search from the field... which is relatively common, but is not going to work during a full reindex. Will need to have a think about that one.

But it needs to be set up as a post-function. The admin script console is just a REPL for testing or running one-time scripts. You need to edit a workflow, add a post-function, script function, then put the path to the file there, then publish the workflow, then test by putting an issue through that transition.

Yes, it is from the script runner plugin... can you upload a screenshot of the config page for the workflow function.

Sounds like you are pasted this into the text box that is for putting in a path to a file. Can you attach a screenshot.

That doesn't make any sense... the line you mention above is not valid. Can you add some logging...

It's in the script binding, which means you just refer to it without declaring it. So just comment out your line 15 and it should work.