Comments
-
I have heard that there will never be a behind-the-firewall version of BB. If Stash supported hg, that would be great. I have experimented with using hg-git to push an hg repo to Stash. It works, but it's not completely satisfactory. But it's useful if you personally use hg, everyone else uses git, and you need to get your…
-
Neena, please could you raise a ticket at https://productsupport.adaptavist.com/secure/Dashboard.jspa. If you bought a commercial licence on the 18th Aug I need to check your organisation.
-
Hi Di - Erm... I believe you can modify the notification scheme such that it will mail an email address specified by a custom field, although the custom field may need to be a User type. Take a look... jamie
-
Hi - you just need to append "&customfield_11111=" + escape("the@email.com")
-
You can override the reporter if you have the right project permission, but the reporter must be a valid jira user, not an email address. But you could set a custom field called say "ActualReporter" to the user's email address, and continue using the generic account.
-
This is not a script runner question... at least the error message you have is not produced by script runner.
-
Interesting but to me that doesn't explain how when greenhopper 5.7 is out of the picture, everything works normally.
-
IMHO this class was doing something very iffy: http://docs.atlassian.com/greenhopper/5.6.1/com/atlassian/greenhopper/dev/Reloader.html - it caused me problems too. Removed from 5.7 and above.
-
Is it definitely "enabled" after the restart? I have seen some plugins that persistently disable themselves on startup, for no obvious reason.
-
Here is code to create a new scheme, and a new level with a single group: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.issue.security.IssueSecuritySchemeManagerimport com.atlassian.jira.scheme.SchemeEntitydef issueSecurityLevelManager = ComponentAccessor.getIssueSecurityLevelManager()def…
-
Your method is very flexible, I agree. Easy to combine multiple groups etc if you need to.
-
Issue security levels can have a "Group Custom Field Value". Why don't you write the customer group to a group custom field (can be hidden), and use that in the security scheme.
-
issueSecurityLevelManager.createIssueSecurityLevel(scheme.id, "Private", "Reporter only") But, agree with Alex.
-
Hi... I think I get what you're trying to do... ie perform a complicated calculation then set a form value. What's the actual problem - you can't get the fixVersions from the form? Try getFieldById("fixVersions").getValue()
-
Can you be a bit more specific about where you need help? What context is this, eg post-function, or behaviour script? It sounds like you need the affected version field, then to work out your numeric value you also need to get the list of unreleased versions for that project, using…
-
I have this problem too since someone create a branch beginning Bugfix/... it's driving me crazy, will try @Balazs Szakmary solution. I've since put in a branch naming standard hook from our own plugin (sorry, cheap plug), but unfortunately too late.
-
I marked Nic's answer as correct as you've cross-posted this last question.
-
Thank you Michal and Nic. Covered here: https://jamieechlin.atlassian.net/wiki/display/GRV/Upgrading+to+3.0
-
The ScriptRunner equivalent is: issueFunction in linkedIssuesOf("updated > -1w", blocks) but in both cases I don't think it's what you want. Both will find the blocking issues where the blocked issue has not been updated in a week. The hard part of your question is the all, ie where all the blocking issues have not been…
-
"git diff-tree -r commit_hash" will give you the hashes. It's already been hashed and stored, so no need to run hash-object again.
-
It's kind of low-level information, I don't see why it would be generally useful. AFAIK neither show it. Why do you want it?
-
As a side note, IMHO you should always prefix your crucible projects with CR-, to avoid this problem. Crucible has a field called "linked jira issue", however filling that in does not make it appear in jira (which makes me wonder what the point is). It only shows in jira if it's mentioned in the description.
-
As Robert says, you get this message if you try to add a validator and there is no screen configured. Possibly it only happens when you specify that the error message should be associated with a field. It's a JIRA bug.
-
There are many different aspects... behaviours, script fields, listeners, workflows. JQL functions, etc For workflows you can grep a db xml backup for "com.onresolve" for instance.
-
For conditions or validations, you'd use the jql query condition. You need to use single quotes around the Chg Request too.
-
Also available if you install script runner plugin (free): issueFunction in subtasksOf("issuetype = Epic") Performance testing shows it's much faster than the other two!
-
You need a plugin, or calculated custom fields. Try: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-hasAttachments([fileextension])
-
They are not encrypted but they are encoded - https://scriptrunner.adaptavist.com/4.3.3/jira/releases/current-release.html#_base64_encoding_for_workflow_function_arguments You can decode them... it doesn't matter if the args are encoded or not in the workflow. It's true that some of the args don't need to be encoded and it…
-
Hey Roy... did you check my answer to your other question? You are allowed to give feedback to answers It really depends what version of Script Runner and JIRA you are using. It's always advisable to use relative paths for this reason, or script roots in version 3 of the plugin. If you have just a few you can edit the…
-
If I understand you. You want to get all the users from the groups in the first CF, then update a user CF with them? Yes you can do that, just get the user objects from groups, then set the multi user CF to that value.