Comments
-
I know you have a solution now, but the answer to your question as written is "unfortunately not". It would be complicated than that because the UI would need to allow "any match", "no matches" etc. Also as you are looking at "siblings", you would need to have a parentsOf and childrenOf in your jql query, and Benji's…
-
We don't support that plugin: https://productsupport.adaptavist.com/browse/SRJIRA-2110
-
You can use com.atlassian.jira.bc.issue.IssueService#validateTransition(com.atlassian.jira.user.ApplicationUser, java.lang.Long, int, com.atlassian.jira.issue.IssueInputParameters, com.atlassian.jira.workflow.TransitionOptions), TransitionOptions has flags to skip permissions and conditions etc.
-
You should use the Fast-track transition script... there are a load of corner cases and this scripts handles them.
-
more info reqd
-
look at issue security schemes... the default level would be "reporter", plus presumably some other role or group.
-
You've asked this several times already.
-
Try this: import java.sql.Timestampissue.setCustomFieldValue(cf, new Timestamp(new Date(2012,9,17).getTime()))
-
import java.sql.Timestamp
-
IIRC you can just add a new header using httpclient. Personally I would forget coding it in groovy until you can verify that you can get a sensible response using fiddler. When that's working, you can compare what jira sends by proxying through fiddler.
-
I think you would need to write a custom function for that. Also version start data is a greenhopper fiction, so should be part of GH really.
-
Yeah, cfValues is indexed by field name not by cf ID. I thought this would be easier for non-techies and might make things more portable when moving configurations from dev to prod etc.
-
Which log are you looking in? What OS are you running jira on? System.out goes to <catalina_base>/logs/catalina.out, or sometimes to catalina.<datestamp>. Have you checked those?
-
I think, not simpler but more elegant and maintenance-free, is to get the list of option values for that custom field and make sure they're all present. I would write a condition in groovy, rather than using the "simple scripted condition", if that's what you're using. Don't have time to write it for you, if I get a…
-
You need to set it to the ID of the option rather than the string "Mechanics". Can you try that, you can get the option ID from the page where you configure the options for the custom field. If that works I'll show you a better way where you can get the option ID from the name.
-
The closest I have to your original question is here: https://gist.github.com/jechlin/8a0f026ac62091b553be - it's a bit old though.
-
I can't write this for you at the moment... there are multiple examples at https://scriptrunner.adaptavist.com/3.1.5-SNAPSHOT/jira/behaviours-overview.html and https://scriptrunner.adaptavist.com/3.1.5-SNAPSHOT/jira/recipes/behaviours.html
-
If you use {jira}ABC-1{jira} it will render it nicely according to the status/resolution. Not sure it will do it if you just use the ID alone.
-
From the stack trace I'd guess that one of your statuses is null for some reason.. Can you login as that user using script runner "switch user" script or some similar plugin and see if you get the same error? Get the user to hit some url that doesn't direct to the dashboard, eg an issue url, and take it from there.
-
I don't think the feature for showing the field in the correct section depending on the template was in that old version...
-
This is done and released in 3.0.6, maybe you need to update: https://jamieechlin.atlassian.net/browse/GRV-358
-
Exactly... if you use the spread dot operator you need to compare with a list or use "in" or "contains".
-
Not sure whether this is the standard projects / issue types dropdowns, but in the standard one you can make it recalculate the issue types by firing the event yourself. Eg to change it and fire the handler: AJS.$("#project").val("10090").trigger("change")
-
I'm aware it's not @PublicApi but I didn't actually write this plugin, I'm just maintaining it as a FREE SERVICE out of the goodness of my heart. I don't even use the plugin. If Atlassian are so bothered about supporting customers that use this plugin maybe they should maintain it. After all it's not a big job.
-
Here is the authenticator class: https://gist.github.com/1722771 Apache config: ProxyPass ajp://$host:$port/$context ProxyPassReverse ajp://$host:$port/$context There are not many places that use PKI... yours is the first I've heard of after mine and Nic's. The people responsible should be providing you with guidelines on…
-
I will try and post the config tomorrow when I'm near it, but it's pretty standard. Use mod_proxy_ajp to proxy to ajp:/jirahost:port/jira You need to open the ajp port in your jira server.xml. We only use https for the /login page, all others get redirected.
-
We used to do it exactly the same way as Nic describes, a custom authenticator that gets the certificate subject, and looks up the details in LDAP. A few months ago I changed it so that Apache does the authentication... there is nothing funky here, two-way SSL in Apache is well-documented. We use ajp to proxy to jira, so…
-
"Exclusive or" is the caret ( ^ ) symbol - see http://groovy-lang.org/operators.html
-
I would write it like this: import com.atlassian.jira.component.ComponentAccessordef doneNames = ["Done"]def issueLinkManager = ComponentAccessor.getIssueLinkManager()def totalSP = 0.0enableCache = {-> false}def customField = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("Story…