Comments
-
What that would do is, any time anyone edits an issue, a new Error issue will be created. I doubt this is what you want? One problem could be that Error is not in the issue type scheme for the project. You need to check the log files... if there are problems with the condition it will show that. No, no imports required.
-
Just from eyeballing them they look fine... do they not work?
-
See https://studio.plugins.atlassian.com/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Clonesanissueandlinks - although it clones all the fields you can override any or all of them.
-
The (rubbish) workaround is to add a trailing space to the title...
-
JIRA has had the benefit of actual UI/UX designers. I would stop trying to second-guess what you think the users actually want and ask them. In the event you get all this work you will just end up with something ugly, confusing and unmaintable.
-
Sorry I normally use ComponentAccessor.getComponent()... try that.
-
As I said: ComponentAccessor.getComponentOfType(myClass) should work fine
-
ComponentAccessor.getComponentOfType(myClass) should work fine - is your component defined as a public <component> in the plugin xml? It works for other types of components from other plugins so should work fine for yours. If you just want a class from another plugin that's not a component you should use:…
-
I'm still testing and this won't be the final version for jira5, but I've attached a (more) working version to https://studio.plugins.atlassian.com/browse/JBHV-100.
-
Yes you're quite right... I forgot you were using jira 5. I will be updating this shortly. I don't think you're building it wrong, it's just that I don't think it's compatible with rc3... it was working for beta2. Will get back here when I can.
-
Hi Andrej, OK... your options are using javascript then, or, this is what the behaviours plugin was written for: https://studio.plugins.atlassian.com/wiki/display/JBHV/JIRA+Behaviours+Plugin .
-
You just want a standard validator module... https://developer.atlassian.com/display/JIRADEV/Workflow+Plugin+Modules That validates data before saving. Not sure what you mean by saying you don't want workflow validation.
-
We are adding support for cascading selects, it will be released soon.
-
What's the question? I don't understand your comment above, and I don't see the debug lines I recommended.
-
> if(tl.getValue().contains('Camera')){ Log to your console t1.getValue(). As it's a cascading select you are probably getting a map or a list. But if you add some debug either you will figure it out or I will be able to.
-
Last line should probably be: issue.setSummary(cFieldValue + " " + issue.summary)
-
If you've got greenhopper, the agile gadget shows this kind of information for the next releases on the Info tab. You can change the version to display, but not as part of config... that's confusing, if you have it try it, you'll see what I mean.
-
Or just: issue.subTaskObjects
-
Short answer is it's not possible, unless you just copy the HTML in.
-
David - yes, some packages were moved, sorry about that but I didn't have much choice. I need to document that. I will make it so that it doesn't add the path twice... I'm not really sure why you got the malformed url exception though, looks ok.
-
Michele - there is information on this here: https://jamieechlin.atlassian.net/wiki/display/GRV/Upgrading+to+3.0(under "script roots" section) - but it's only pertinent to the new beta version. You can download it from the same page if you have a recent enough jira instance. For the current version you need to compile a…
-
Would probably work providing no one changed this field, or you had a listener that copied the field wherever it might change.
-
Same as the other question, answer is in https://developer.atlassian.com/display/JIRADEV/Custom+Fields+that+use+CSS+or+JavaScript+Web+Resources+in+JIRA+5.0. Use a live() handler for "change" or bind to JIRA.Events.NEW_CONTENT_ADDED.
-
Drop and recreate an empty database, then go through the xml restore process again. It can't pick up where it left off...
-
If you have crucible and jira running on the same machine, but different DNS records, it's not something you can configure in jira or crucible (assuming you want them both on the default port). Look at running apache on port 80, and proxying via ajp or http, using vhosts. BTW I am not trying to give you an enhaustive…
-
It's not 1, it's "1". It's the difference between an integer and a string. Javascript will coerce it for you so that's irrelevant anyway. The above is javascript not JQL. I was only trying to give you a starter for 10, I haven't got time to write it for you completely.
-
Why don't you use jquery as below. Also your 1 should "1" as the priority value is a string. Not complete example: (function($){ $(function(){ $("#priority").change(function () { if ($(this).val() == "1") { $("#description").closest(".field-group").show(); } else { $("#description").closest(".field-group").hide(); } }) });…
-
Possibly typo of "1 - Very hight" ? I see you asked and resolved the same question on our support portal, perhaps you could share the solution here.
-
I wrote up how to write queries like this: https://jamieechlin.atlassian.net/wiki/display/GRV/Scripted+JQL+Functions#ScriptedJQLFunctions-MoreComplexExamples Hope it helps someone.
-
The next version won't require the second param, in which case it means: work across all link types