JamieA Expert

I'd have a look at the REST tutorial. The "wrong" way to do it is have your javascript generated by a velocity template, which has access to the java objects. The "right" way is to write a REST module, when your dialog is opened it makes an ajax request, receives JSON, and displays it as it needs to.

You can use the jql function: commented, eg issueFunction in commented("by eviluser"), and feed the list of issues into the script Monique posted. Filter on comment.author rather than comment.body

In what context, are you running this in the script console? "issue" is only a bound variable in workflow functions and script fields etc, where it makes sense.

Hi - for this type of script you don't need server access, because you can paste what you need in the script runner admin panel. You won't need 90% of the code in that script, it's all to support the optionality and different types. However you should test on a local instance... it's easy enough to run one. I would just…

I think you are talking about the Copy Custom Field Values built-in script? If so it doesn't support copying to or from system fields. There should be dropdowns with the possible fields, if it's not in there it's not supported. Sounds like it could be useful though. You could write your own script...

The XML export/import will probably run out of memory, at least it did when I attempted a similar size migration. However it's the easiest option so give that a try first. But you could move the instance to linux and get all the good stuff without actually moving the database, you could leave that on sql server. At least…

Shut down the old one? Is it an inplace upgrade or a separate second installation?

Not sure originalProduct is - I think you want ModifiedValue as you had, but pass in a genericvalue for the new value.

It seems to want a generic value, not a Project object or Double. Have you tried setting it to project.getGenericValue() ?

You should add some debug, eg to log the value and type of the severity FormField. I expect it will be a string, so severity.getFormValue() == 1 won;t work, you should use: severity.getFormValue() == "1" But you should still add some logging... eg log.warn (...)

Do you have full LDAP integration? Or delegated LDAP integration. I'm really talking only about the former here... with full LDAP integration jira will just remove them from the directory, causing various buggy behaviour.

That's fine but my point is I have no control or influence over AD, so I cannot disable them and prevent them being deleted.

I don't think I said that internal and external directories could not be used together... what I said was that you could not create more than one purely internal directory. And I want the "Retired Users" directory to be a component of the LDAP directory and handled entirely by jira. When a user is deleted it should be…

Confirmed bug.

This happens if you try to submit when it's in the process of sending a request. Try putting the behaviour not on the assignee, but on some field that's not likely to change. I think you can put it on the project.

That's pretty cool, although horribly unmaintainable ;-) Can't help thinking you just need a condition though.

That's true. I would just put the message under the summary... currently behaviours doesn't have support for sticking the message at the top.

Use a workflow validator if you want to do this, don't use behaviours. If you use a validator then yes you throw an InvalidInputException.

Well done Mizan ;-)

Make sure you provide the full path to the file as it is on the server... Also look in your log file for error messages... doing this without feedback is like trying to play chess without being able to see the pieces.

If you are willing to give up so soon without asking for any help, I really don't know what the right system is for you, but good luck in finding it.

The extension has to be .groovy so the system knows which interpreter to invoke.

It seems to me that you are trying to show what's in currently open sprints, along with their Epics? And the problem is that Epics are not returned by "sprint in openSprints()", because they can span multiple sprints. > In "columns to display" I would like to display the "issues in Epic" but it isn't an option Because it's…

Yeah, use a listener. See https://jamieechlin.atlassian.net/wiki/display/GRV/Listeners

You could try: https://jamieechlin.atlassian.net/browse/GRV-13 I don't think I got round to integrating that code. Failing that you could add listeners, but I don't know how to distinguish events caused by mail handlers vs standard events. You could try checking transientVars and see if there is anything in there.

What's the result you're getting? I'm not sure what you need help with to be honest.

The problem is just that getCustomFieldValue is declared as returning Object - see https://scriptrunner.adaptavist.com/latest/jira/#_providing_type_information

I don't see a problem having a scripted field. Here's code that works for me. Use the "date time range indexer", and the "date" template: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.Issuedef customFieldManager = ComponentAccessor.getCustomFieldManager()def sprintCf =…

"is Epic of" or "has Epic" for the second argument, can't remember which.

The second one is optional as of some version... either update your SR, or you need to specify the link name.