Comments
-
Not sure... I can't think of any plugins that have a custom field type and their own searcher, and aren't really complicated. What's your main problem again, performance?
-
That seems to be how to re-use one of the bundled searchers for your custom field type.
-
Or you can create a listener that does that for you, rather than periodically with a service.
-
You need to make sure that the second one has a mutually exclusive condition to the first one. Only one of these should be allowed to execute.
-
You need to make sure that the second one has a mutually exclusive condition to the first one. Only one of these should be allowed to execute. And please tag your question with the plugin's tag.
-
Setting up external POP or IMAP servers is blocked... this question was asked only yesterday. See http://confluence.atlassian.com/display/AOD/Restricted+Functions+in+Atlassian+OnDemand#RestrictedFunctionsinAtlassianOnDemand-JIRA @Jeremy, this thing is just becoming a bad version of the old forums without a working search.
-
Roy - check your permgen settings. If your machine has enough memory I recommend 512m.
-
In theory what you are doing is possible, but a little bit fraught, and I guess you have run into problems already. This was a promising plugin: https://plugins.atlassian.com/plugin/details/5115?versionId=11213 - but is discontinued, or support seems to stop at jira 3.13.5. In the organisations I've worked in the support…
-
Well, sometimes it shows atlassian-group-role-actor, in which case you need to look up members of the group. > My requirement is to select a list of users(using REST or SOAP) for whom I can assign an issue from my remote system That's normally the developers role, but not always.
-
Get all the roles with: http://docs.atlassian.com/jira/REST/latest/#id2475420 Then iterate through them using http://docs.atlassian.com/jira/REST/latest/#id2475480
-
When jira was set up the projects gadget was on the system dashboard, configured for all projects. I used the script below to remove it from all dashboards and replace it with a text gadget explaining what had happened and why. I can't remember when I ran this, the code may need updating for 4 or 5. I know of no better…
-
I don't see how that's the variance... that's just (resolved - created).
-
I feel like I should make a t-shirt saying: "What kind of field is it?" But to check it has some value, you can just use: cfValues['DeployedBy'] You don't need to compare with the empty string... if it's empty it will be null. Use built-in scripts -> Condition Tester, and asserts (see docs).
-
3 and 4 are answered here: https://answers.atlassian.com/questions/13147/is-subversion-repository-being-backed-up?page=1#13150
-
Easiest way is just to delete all rows from the filtersubscription table.
-
I created https://jamieechlin.atlassian.net/browse/GRV-457, it will be in the next release.
-
Doesn't seem to be in the binding but I agree it should be.
-
https://scriptrunner.adaptavist.com/latest/jira/quickstart.html
-
Do you mean the incoming links? These should be displayed anyway. I just released a version of the script runner that lets you use groovy to write the values for custom fields, there is a vaguely similar example to what it sounds like you want here:…
-
If you use this: log.warn "Validate: " + workflowTransitionUtil.validate()log.warn "Progress: " + workflowTransitionUtil.progress() do you at least see those lines?
-
Sorry Kim, you are in the right place for support here... this is not covered in our support remit. We will get to this question.
-
oh ok I missed that. Should be fine then. Check the output from .validate() and .progress, eg: log.warn workflowTransitionUtil.validate()log.warn workflowTransitionUtil.progress() then check the log output.
-
you're better off using the "fast-track" built-in script. It's tricky doing a transition within another transition. If you refresh the issue does it work? How about change it then refresh?
-
Check the logs for the reasons why it didn't fail. Expected errors, eg permissions errors, won't show as failures.
-
The deprecation warnings are correct. If you change it as recommended, it should work in JIRA 8 but may not. If you don't change it, it may not work in JIRA 8 but probably will. So, meh. Changing it as recommended should work fine though, you need to tell us how it errors out.
-
so you just need a script on the sub-task workflow. You can either hard-code the action ID or look it up by name from the WorkflowManager).
-
correct, sorry I missed this when I posted.
-
WorkflowTransitionUtil.setIssue(parent) should be workflowTransitionUtil.setIssue(parent) ie a small w.
-
I had a similar problem, and if IIRC, I had to replace the line breaks with \\ and then newline, in the word doc before the import.
-
I would guess that due to firewall issues, that will almost certainly not be possible. The ondemand server needs to be able to speak to your server. But if you are paying for a wiki component, why don't you just dump your wiki to xml and have support import it? Then you don't need to worry about upgrades and availability…