JamieA Expert

There was a question on this recently, but I can't find it. You need to the nest the query. Maybe try from the perspective of the bug, and use the filter query to find stories then epics. This is certainly possible.

This question has been done a lot... take a look at some of these hits, particularly the third result: https://www.google.co.uk/search?sourceid=chrome&ie=UTF-8&q=site%3Aanswers.atlassian.com+split+server+hardware

The solution would involve: def changeHistoryManager = ComponentAccessor.getChangeHistoryManager() def changeHistories = changeHistoryManager.getChangeHistories(issue) def previousAssignees = changeHistories.collect {history -> history.getChangeItemBeans().findResults {ChangeItemBean change -> if (change.getField() ==…

Great description of the problem and solution ;-)

Why don't you just do it in the database... count (*), summary, group by summary having count(*) > 1.

This was bad, it was broken - it will be fixed in the next release, please add yourself as watcher to https://jamieechlin.atlassian.net/browse/JBHV-312 I infer from this that there was inadequate regression test coverage but also that they are rarely used, as you can check for this stuff in the server-side script.

I'll look into it... 5.0.2 has not been tested much.

There is a long conversation about this here: https://studio.plugins.atlassian.com/browse/JBHV-134. As I said, shortly this will be easier: I'm going to reopen this because I am adding new APIs: getAction(), getActionName(), getDestinationStep(), getDestinationStepName(), to make this much easier. But, if you're only…

yes, this is the love I was referring to... I hope I will have time to fix it but not sure exactly when.

> Is it true that hiding custom fields using Behaviours plugin will disable bulk edit (or bulk move in our case) for all issues across all projects? No, it will disable inline edit for fields where the behaviour is applied. Inline edit is completely different from bulk edit. Behaviours doesn't work with bulk edit, which is…

The issue type to create from emails is one of the parameters of the email handler, under Services.

To be fair to Atlassian, the 10k number is the upper limit that they have tested with: http://confluence.atlassian.com/display/JIRA044/User+Management+Limitations+and+Recommendations - so perhaps not surprising it didn't work in my environment.

Works ok-ish, but it depends on how many users you have in the directory. We have something like 100k users and performance was an issue. In the end I gave up, although the main reason was https://jira.atlassian.com/browse/JRA-25915 (which looks like it's going to be fixed soon). IMHO this is getting better all the time,…

It will work fine but I recommend you use @Grab. http://groovy.codehaus.org/Grape

They weren't there previously... someone must have added them. I know of a few people that did that. Consider upgrading to 3.0-beta, which does include them, you can get it from here: https://jamieechlin.atlassian.net/wiki/display/GRV/Upgrading+to+3.0

Sorry this was so painful... right now this is about the only way to do it. The confluence version of this plugin handles this sort of thing much better - eventually these changes will make their way to the jira plugin.

It's not very simple in OSGi world. You might want to put the jar in WEB-INF/lib, and try that. You should also exclude groovy itself when Grabbing http-builder. The complete list of dependencies is below. [INFO] The following files have been resolved:[INFO] antlr:antlr:jar:2.7.7:compile[INFO] asm:asm:jar:3.2:compile[INFO]…

No,. that's just the syntax highlighting, which is showing that 'Bug' is a string literal. There is no problem there.There should be a preview button when you can test if the condition evaluated to true or false.

I don't really understand what you mean, or rather where you are adding these values, can you post a screenshot?

There's lots of different ways of doing this. Let's say you you have done it by creating a notification scheme with different events, where you are specifying the recipient. Then you would have two Fire event post-functions (or listeners) with different conditions, which would fire the appropriate event. Condition would be…

Yep, exactly... you need to specify the "subtask summary" field for the reopening to work. It's designed for when people want a finite list of simple sub-tasks like "Approval", "Analysis" etc. The code is pretty straightforward.

> Everytime I perform the transition, the script creates a subtask although it exists. It tries to reopen a subtask with the provided summary, yet you are appending some string to it. What does "subtask summary" field look like, does it include your "- X" ? For this feature to work you have to set the subtask summary to…

Indeed! It could also be done with the jql functions in script runner: issuetype = "Story" and issueFunction not in hasSubtasks()

See https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/simple-scripted-validators.html#_subtask_relationships - towards the end of the section there are examples on checking parent status

date fields don't have a "time" component, so it's not really important. If you're adding 7 days to a date, the timezone is not relevant.

A cast won't work, use a SimpleDateFormat to convert to a string. But you may need to check the default date format that your jira uses. There should be a simpler way, but I don't know what it is.

Yes... generally it matches what the browser sends. Examples for date and datetimes etc: inputParameters.with { setOriginalAndRemainingEstimate("4d", "3d") setDueDate "18/Nov/12" setAssigneeId adminUser.name setSummary "updated summary" setProjectId project.id setIssueTypeId issueType.id setReporterId…

Oh... that's surprising. You can do a lot with that custom html thing, and difficult to see why it's restricted. It's not as though it parses velocity or something.

I'm not familiar with the SaaS confluence, but I believe the custom HTML is not disabled, in which case that's the best way for this particular task. Admin -> custom html -> add the javascript to the section "at the end of head". For the theming in general, as you probably can;t upload plugins, the best way might be to do…

Not all custom fields, just ones from plugins it doesn't know about.