JamieA Expert

Not all conversions are supported - you could modify the code to put the cast in...

Try the copy custom field values script from the script runner plugin. This will handle a bunch of conversions, and doesn't need any downtime. So you would create a new field, copy the values, delete the old field, and optionally rename the new field. Some conversions you can do by changing the database customfieldtype…

What version of jira? It's possible that it's not working in the most recent. It's very hard to keep track of the UI changes... there is no concept of a public API for the DOM.

I heart the 404, which is good because I'm seeing quite a lot of them after the redesign.

It would be hard to imagine the admin UI that would allow this to be done without any programming. A new calculated custom field type is a big deal though, unless you're very familiar with jira. It could be done with just javascript though, although what you'd get would be a deal less powerful than a calculated custom…

Could be done with my not-yet-released scripted custom fields maybe. The result from that can be stored in the index as a string (changelog comment) or int (changeset id), which would make it queryable.

Hi Francis. Well, in the svn plugin code there are methods for getting issues with commits for particular projects, so I'd look at making that into jql functions. With fisheye I don't think it's possible as AFAIK nothing is stored in the lucene index, so this sort of query really needs to be made from fisheye. Everything…

How are you integrating with the VCS... eg if using the jira-subversion plugin it feasible, as the commits are indexed. But if using fisheye I doubt it is possible.

You can add the field called "Linked Issues" (or similar in your locale) to a screen, which will let you add issue links without doing a separate operation.

this is not very clear, add some sample output...

Validating attachments and links added this transition does not seem to be possible using the JIRA API... short of examining the HttpRequest, which is a bit hacky and doesn't work with REST. If you look for an answer on how to validate that a link has been created, you can use the same technique.

Don't forget to close your connections in a finally{} block...

Yeah, that's a frickin pain. It's the same for workflows. IMHO jira should trim these before it stores them.

See https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-PowerAssertions Show us the output when you do assert the above in condition tester.

Also please try to avoid creating duplicate posts when people are already trying to help you on your other question.

See See https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-PowerAssertions Is "list1" really the name of your custom field? It's case-sensitive.

The condition would be: issue.key.endsWith('0') What have you tried?

Jamie actually. Questions about using httpbuilder have been asked before... can you search for that first to see the fun and games involved.

or "issuetype in standardIssueTypes()" If you use the function it should not matter if you have Bug as subtask and parent type.

It certainly won't work. For one thing, the Lucene index will not be notice updates in the database beneath it. Various caches will not be filled etc. It's probably suitable for use as the database for a cold standby, but you won't be able to do replication through it. Why can't the remote sites use the central confluence?

If you want a comment: that's a seriously expensive plugin and it's not clear what it does over the free jira-svn plugin. You should make that explicit. Probably only large companies are going to be in the market for this sort of thing - most small shops have moved to DVCS. And large companies are going to be scared off by…

But customer should bear the cost of the escrow service if it's not already set up.

Confluence backup does backup personal spaces....

You're doing a pattern match on a list, which won't work. You want something like (untested): if (issue.issueTypeObject.name == "Library"){ issue.componentObjects*.name.every { it ==~ /Library.*/ }} else { true;}

I don't know the answer, but in the script runner plugin you could use "Simple Scripted Condition", where the condition would be: issue.componentObjects*.name.contains("Requirement") Which would mean one component would need to be Requirement. If you wanted to only allow the transition if that was the only component you…

After changing them to have the same name, customers now need to be re-educated that they're actually different products?`It's not really surprising if people expect feature parity.

Copy project from the script runner plugin works with jira 5. That works for me... but probably agree with you that it should be a core function.

2.0.7 was never available for 4.3... choose the right version for your jira from https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner.

Yeah, it was a different problem than I thought. But I think that version is only for jira 5.1+.

Weird. What's your jira version and plugin version?