Comments
-
The latest version is beta-8. The only beta aspect is the jql functions, but I think I am more or less done with beta testing anyway. But yeah, it requires 5.1.
-
You can't do arithmetical expressions in JQL. Script runner jql functions include expression function, there's an example for almost exactly what you want to do in the docs.
-
You can't do either of the above in OnDemand.
-
I think there are several different possibilities here. When you say "verified" do you mean tested? Or just merged to that branch... Where is the list of branches that each fix must go through defined...? Is that a decision on an issue by issue basis? Or can that be inferred from the branch naming convention that we had…
-
So I don't know why it's using / as working directory. The script paths are resolved relative to the working directory, which is normally but not always catalina.base. Not sure I would worry too much because this changes in Script Runner 3.0. > is there a way to specify an env. variable in the script path i.e.…
-
yeah but it should... that was all I could think of at the time. Run this in script console and let us know what it reports:System.getProperty("user.dir")
-
It should work.
-
Bearing in mind that closedSprints() is quite broken, ie "not in closedSprints()" doesn't return issues that have no sprint defined... A possible solution is: project = SCA and sprint is not empty and issueFunction not in inSprint ("Some board name", "Backlog") But you need to install the script runner plugin, and you need…
-
That doesn't include sprints that are not started.
-
If you use the plugin's tag you will more likely get an answer. I don't really understand your question but I think you are talking about the behaviours plugin. When: choose a transition When: choose a status They will be or'd together.
-
If you are using ScriptRunner, then https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html
-
Options are javascript to set a value if none exists, or behaviours plugin to do it. Behaviours script example: def summary = getFieldById("summary") if (! summary.getValue()) { summary.setFormValue("Summary template...") }
-
Hrm, but you can't create an issue without a summary... also seems painful having to do a transition just to enter summary and description.
-
See https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/validate-attachments-links-in-transition.html#_validating_links_added_this_transition
-
There is information about this scenario here: https://scriptrunner.adaptavist.com/3.1.5-SNAPSHOT/jira/recipes/workflow/validators/simple-scripted-validators.html#_checking_linked_issues
-
That sounds plausible... Maybe best to put it as a condition of the outward transitions from open? It should be possible to get the link even though it's not committed yet, I will have a dig around.
-
I would just use the "create a subtask" built-in post-function on the Create step, then the user doesn't need to do anything, if you only want to create a subtask. If you want to create an issue link, that's possible, but it needs to know where to link to.
-
Hi Janine... can you explain again what you need to do? From your question I thought you wanted to validate there was a certain type of issue link for a certain issue type, but your code is creating a link.. and also creating it to its subtask, which I don't think you want. BTW I think you are getting there, we just need…
-
What Ramiro is suggesting I believe is that you use the simple scripted validator function from the script runner plugin, which you can put on the Create step or whatever. The "issue" in the script refers to the issue currently being entered. This will enforce that there is one outward link of whatever type you need. You…
-
Yeah, you can put whatever script you like there... no constraints, eg: if (issue.issueTypeObject.name == "Task") { return issueLinkManager.getOutwardLinks(issue.getId())*.issueLinkType.name.contains('Duplicate')}else { return true}
-
I couldn't get the trick of disabling indexing mentioned in that bug report to work, hence I modified the classes themselves... FWIW, from 4.2.4 to 4.4.3 took around 24 hours, 300k issues, 74Gb ram on the box, about 8Gb allocated to jira iirc.
-
Do you mean loading the XML data into the database or the complete upgrade process? If the latter then I think your problem is JRA-25122 - ie the database is unnecessarily indexed multiple times. In your case maybe 12 or 15 times. Other than the approach that I took which is to modify the upgrade task classes so that they…
-
We have a reasonable amount of automated testing, but every transition of every workflow? No way...
-
There is no way that will be common across all plugins... eg: For plugins that provide workflow functions, scan the XML of all workflows looking for the classnames in the plugin. If you find any verify that those workflows are in use, and how many issues (recently updated preferably) use those workflows. Possibly you might…
-
It's not that straightforward to get the user object from the displayname, and apart from anything else they are not unique. Probably the best you can do is iterate all users and find the one with the matching display name.
-
Maybe that functionality is not in on-demand, according to another question. In that case I'd guess you need to roll your own using webservices. Painful.
-
Export to CSV, then go to Admin -> External System Import -> Import from CSV.
-
This one is also good for older versions: https://marketplace.atlassian.com/162 Although called "search and replace", it can be used just to search in wiki markup.
-
What versions are in play here? Yes, definitely tail the application log, if it can't transition it should report why not (in the latest version).
-
Is there a condition on the action that goes to Open, like "only assignee" or something? Your question seems to imply there is. To test your theory can you temporarily remove that condition?