Comments
-
You need the "number of attachments" custom field from the jira toolkit plugin. If the field doesn't show up ensure you have associated it with the correct project. Personally I normally make this a global custom field but don't put it on any screens, so it's only available in the issue navigator (and for searching).
-
Think you'd need to write a calculated custom field with a renderer/template that fetched the url into an iframe.
-
Do they show up in the remote links? Or do you just mean the address is linked in the text of some field? I guess you mean you want to show them is the results, rather than filter by them?
-
You could try linkedIssuesOf in the latest script runner... eg issueFunction in linkedIssuesOf("status = Open", "blocks") and resolution is empty
-
The example given in the UI itself for adding a comment is: issueInputParameters.setComment('Write your comment here') You've given a stack trace for code that you have not provided, but given us no logs for the code that you have provided, which makes it a bit difficult to help.
-
Try creating a local clone of the repo using svnsync or svnadmin dump and load. Then have fisheye scan it using the file:// protocol, when it's up to date you can switch back to the remote repo. But "scanning for days" is pretty much standard fisheye behaviour in my experience, particularly if you have many tags/branches.
-
Lacking dev ninja skillz, a few stack traces using "jstack pid" might well point to the culprit.
-
you're welcome.
-
I thought you were asking about how to run a query? It sounds like you are using it as a condition or something. Can you attach a screenshot, and describe more what you're trying to achieve... ta.
-
project = XYZ and issueFunction in hasAttachments() With a user: project = XYZ and issueFunction in fileAttached("by jbloggs") See docs: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted%20JQL%20Functions#ScriptedJQLFunctions-fileAttached(attachmentquery)…
-
As Peter said, we have made this easier in more recent versions. If you want to stick with an older version you can render wiki markup to HTML using https://answers.atlassian.com/questions/314932
-
Line 2 should be getFieldByName too I think...
-
-1 sounds suspicious, that's not a valid option ID. What does log.warn(pro) say.
-
Does getFormValue() return anything? you should also log.warn (pro) to make sure the field is actually found...
-
Hrm, getValue() was introduced partly to avoid this need to look up an option by ID, or to hard-code an option ID, which makes it hard transferring code from dev to prod. If you print the value that getValue() returns, you might find it's not a list, or it doesn't contain what you think. Add log.warn ("value returned was:…
-
It sounds like you want to default the subtask with certain values from the parent but allow them to be overwritten? If so this is where the behaviours plugin comes in.
-
&& issue.projectObject.key == "ABC"
-
It should work fine. Use an assertion to test as per https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-PowerAssertions
-
Can you post what you are using. cfValues['A Radio Field']?.getValue() == 'Yes' should work fine.
-
Use: cfValue['Answer']?.value Use Admin -> Built-in Scripts -> Condition Tester to make sure that is evaluating to what you expect... > Ok, but how do you get the value ? cfValue['Answer'].value ? > Answer o Yes o No I didn't understand this...
-
It should be cfValues (plural)
-
The accepted answer is correct for radio buttons.
-
The key question as Thomas says is "what kind of field". You can do log.warn cfValues['Standard Request'] That will give you the class name, from that you can read the javadoc to see how to get the string value or values, or whatever.
-
Fair enough, I see what you mean.
-
They seem to be recommending people contact support for this, but can't you just download the version with the fix and the previous version, and create your own patch file? Should be obvious which class it is.
-
"firstCommented" can be thought of as a custom field, although it is not one. It's something you can use in your queries as described at https://scriptrunner.adaptavist.com/4.3.1/jira/jql-functions.html#_dates. dateCompare does not support that field type "Date of First Response" - there are various issues to get…
-
You could try the scaffolding or zones plugins (google them) but I don't think either are uptodate with respect to confluence.
-
Eva, only users with the "View Source" (or similar name, can't remember right now) can see those tabs. So generally the clients for your client-facing projects wouldn't have the Developer role. Or you could create a permission scheme that specifically excludes clients from that permission.
-
Use .assigneeId rather than .assignee
-
Oh I see, I'll think more about it.