JamieA Expert

I wouldn't have thought so. > I have done. I've done single changes everywhere I don't really understand what you mean - did you try the same workflow on another project and it worked, or it didn't?

Well... something must have changed if it was working. You may have to rack your brains a bit more. Can you try the same workflow in a test project?

Is this a function from the script runner or some other plugin?

I'm a CLI guy too, and I'd recommend your guys become so too if possible... As well as what Chris says, we all use "git up", or for windows, which will update all your branches, including stashing changes if necessary, and rebasing your feature branch if you are sharing it. Then generally we rebase our feature branch ("git…

No implications, it will work fine without GCF. However we use GCF as a matter of course and I have not seen these problems in jira. There are problems in Confluence though with editing office documents, where the plugin says it only supports IE8 and FF", but the user thinks they're using IE8.

It's difficult via a jira plugin because you can't (easily) listen for "project create" events. Best bet might be to use the remote API to create the project and the 5 issues in one shot. If you're not particularly a programmer the easiest way to do this would be with the JIRA CLI (google for it), where you could put all 6…

I just don't see how the rest api comes in to this.

Note to CQ admins - I pressed the wrong button, I meant to flag it NOT as spam, but no way to undo. OP: Can you be specific? It has a rest api, but doesn't directly call jira's rest api.

jql query "status = Closed and status was Reopened". You need jira 4.3 or above.

Add custom script workflow function: issue.setDueDate(new Timestamp((new Date() + 14).time)) Make it the first function. I took this from https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/postfunctions/set-issue-attributes.html

https://answers.atlassian.com/questions/22652286/it-appears-to-me-that-cloned-issues-do-not-receive-the-source-issues-security-level.

Brian - what version of the plugin are you using?

In recent version it's available as *sourceIssue*

try: transientVars["issue"].key This should give you the key of the issue that you are cloning from.

You can add the "Issue links" (or some similar name) field to the create screen, providing you are on jira 4.4 onwards.

https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/select-list-other.html That covers showing a field when an option is chosen.

I believe there is a hard-coded list of field types (ie field type interfaces) that greenhopper supports for adding to cards... Without modifying the source I doubt you can do anything about this.

Did you install the ScriptRunner plugin from marketplace? This plugin provides those functions.

You can do it with ScriptRunner's JQL functions, in your case: issueFunction in linkedIssuesOf("component = XYZ", "is Epic of") docs: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-MoreComplexExamples

I don't really understand this one, script fields have never been able to appear on cards. Can you add a screenshot from a working version perhaps? Mark is referring to the JQL functions below, by the way.

Whatever the workflow action does, maybe you can implement it as a listener. Then at least you can have some projects that use this workflow, and others not, but the others can still comment.

Sure: https://marketplace.atlassian.com/plugins/jira-timesheet-plugin

I'd use Andriy's timesheet plugin. Search for it in marketplace.

Create a file <jira-home>/jira-config.properties with the contents: jira.websudo.is.disabled = true Restart.

I agree, it is annoying.

issue.getCreated().format("dd-MMM-yy")

This is a rare occasion when you cannot use the property syntax - see my comment here: https://answers.atlassian.com/questions/251026/script-runner-how-do-i-pull-created-date-information-from-an-issue Also, because OSWorkflow mangles the parameters, you need to do: <% out << issue.getCreated() %>

Yeah... possibly some database problem then...

I had something that is possibly similar, but also possibly not. Are the members of that group all lower-case? I had users that had got created with some upper case letters, and I think a jql function gave me a similar error.

Is the description in a dialog box very user-friendly? You'd need some option to say "don't tell me again". In the behaviours plugin you can write text under the field where the errors would go, you don't have to use the plugin, but the code is like: field.parent().find("div.jbhverror").remove();var helpDivs =…