JamieA Expert

java 6 may well cause this.

You can put groovy in the groovy box, or velocity in the template bit. I would try to do it in groovy alone and see how you get on. Go through some of the examples... there are too many wrong things here to call them out one by one.

Providing you've set this up correctlu, ie they are the correct workflow actions and you have mapped the behaviour to a project / issue type, the problem is more likely to be the field type or something. Because there's no such thing as a custom workflow, any editable workflow is by definition custom, and they all should…

I would switch on: getIssueContext().getProjectObject() which should give you a Project... IIRC initialisers fire when the project changes, so that might be a good place to put it. Mikey's answer should work too I think.

It's the issue collector plugin - it will create issues in some jira instance in some project, probably your own instance. You would have to look at the issue collectors that are configured. Check the javascript for this, possibly in the announcement banner, it might give you a clue.

Think there is some setting in GH - https://jira.atlassian.com/browse/GHS-2142 However our version didn't have that, so I adjusted the workflow to set it to zero using "Update issue field" post-function, or Resolve and Close.

Writing a groovy script is an option, but creating a project is a hard place to start because it involves lots of maanger classes for all the schemes. If you're looking for "not elegant" I'd think just take a look at using curl/wget - do it before upgrading to 4.4 because it's 10 times more clicks to create a project in…

Personally I would write a groovy script but if that's not your thing you could do with the JIRA CLI. Quite possibly that won't let you set the schemes you need to but Bob would have a better idea. Worth a look.

Yes and yes. I doubt it. If you just want the workflow XML you can get that from the view workflows page, although importing it into another instance can be a pain.

They will be able to give you an XML backup of the database, which contains all the workflow definitions.

! (issue.projectObject.key in ["ABC", "DEF"])

Script runner can verify on a transition that an issue is linked and the issue is in the correct status. It can't do anything about preventing linking to an another issue when the user does More Actions -> Link Issue... So it's useful for enforcing business processes, because normally you will want say a linked Test Record…

PS - this should be considered a bug in the csv import imho.

The resolution is set to some value. My guess is it's set to the string Unresolved, whereas unresolved should actually be represented as null. There is a mention of that here, along with a possible fix (plugin install required):…

it probably escapes your html tags...?

You could... * Install the Script Runner for Confluence * Go to Admin -> Script Console then paste in and run the following script: package com.onresolve.confluence.scriptsimport com.atlassian.confluence.pages.TrashManagerimport com.atlassian.confluence.spaces.SpaceManagerimport…

Surely you mean kosher? But kusher is a new word for me, so thanks for that. FWIW, it's fine with me.

I'd start with https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/simple-scripted-validators.html#_checking_linked_issues.

duplicate of https://answers.atlassian.com/questions/31213/problem-creating-remote-pages-in-confluence-usin-jira-both-on-my-local-server

Thanks for the mention Blazej. But yes, afaik this is not possible in AOD.

I would contact Atlassian Support, you probably won't need direct db access.

what browser?

you're clicking the little edit icon right? Are there any javascript errors?

No... because the issue navigator only works on issues, but you want to query and select just worklogs. You can select issues by worklogs but aggregateExp works on issues, so it will sum up all the worklogs. The only way I can think of to deal with this is to write your own gadget or report.

I'll take a guess that fisheye is set up to scan for commits every one minute which is the default, and you haven't changed it... If so, did you set fisheye up yourself? Is it possible that it's pointing to replica repositories, maybe for performance reasons, that get synced overnight? Assuming you have admin rights on…

As well as the number in parens, the thickness of the line gives you a visual cue. If you've got good eyes.

Yes, Dieter is right. But it only allows you to filter on transitions N days before now, I guessed Ryan wanted more control than that. Thanks for the plug though Dieter ;-)

Hrmmm... are the names exactly as you have them above?

Does the error only happen when one of them is zero? You also need to handle the case of them being zero, as well as null. Try something like the following, if it doesn't work can you post the stack trace... def urgency = getCustomFieldValue("Urgency") ?: 0def complexity = getCustomFieldValue("Complexity") ?: 0def need =…

Not really... I guess when we start working on it we'll know how to do it... nothing I can share at the moment. I doubt you will be able to fix this issue using the current API.