Comments
-
Possibly just because they haven't tested with it, more than it definitely doesn't work. Try it.
-
Right, they say nothing about IE8 being a poor 4th or 5th choice for use with the products.
-
It would be great if Atlassian fronted up and said that at least some of its products, eg Greenhopper and Crucible are not really compatible with IE8. Would help in the continual battle to get a modern browser into corporate environments. Or at the very least, they could say it's usable but the experience is severely…
-
Hi Madhu... that's just a warning to tell you that we can't offer any coding assistance. There's no possible way of telling which field you meant when using cfValues with a name. You can just ignore that warning.
-
We can come back to the Condition Tester when we've worked this out.
-
> This was working fine and simply stopped working since the upgradeCan you explain more how it's not working? Earlier I thought you said that it's getting the wrong custom field.
-
This is a workflow function? cfValues is populated only from the fields associated with the issue. Are you sure that both Severity fields are not associated with the issue, even if only one happens to be on the screen? > We noticed the problem since we upgraded to JIRA 6.4.9 on the Script runner 3.1.4. What version were…
-
You need to write your own... you might want to ask a new question.
-
That bit of the plugin is not open source atm. Try to find a plugin for a custom field that ships with its own searcher...
-
You could use hasPermission(browse) for each of the issue IDs. But it's going to be very slow... what's the performance like returning 40k literals? I found it incredibly slow. You can use a custom field and write your own search, and return Lucene terms which is much faster - that's what I did for the script runner…
-
It doesn't support the universe of fields provided by custom plugins. This is one it's never been tested with. You can create an RFE at https://jamieechlin.atlassian.net/browse/GRV if you want it on our backlog. > The setHidden() method works, but setRequired(false) doesn't work Also note you can't override the…
-
You should use: cfValues['Requested daytime']?.value= ... unless you know this field will ALWAYS be filled in. I don't understand the difference between a good and bad issue. I think on such an old version of jira you just don't want .value. You will need to change that when you upgrade to 4.4.
-
You wouldn't get Atlassian support for this version of jira, and personally I'm not inclined to either, it;s just too old, and too much has changed.
-
It's platform dependent but that's not my point, my point was not to use println and expect to see the result on the screen. >> My function Do it one clause at the time, in the condition tester.
-
This is correct: cfValues['Requested daytime'].value if it's a select list or radio buttons etc. The return type of "println" is void, which is why it would show null. If you open the catalina.out file you would see the output there. Try using an assertion in the condition tester:…
-
I don't think it makes a blind bit of difference to performance, and I doubt there is a tipping point. All jira is needs to do is stream the file when the client requests... not demanding. Obviously it will have an effect on the disk space you require, but I presume you've factored that in. The only possible difference is,…
-
Hrm... a better option might be to default some field to the issue that is currently being viewed with javascript. If not, I don't know whether you can get the currently viewed issue from the user's session, although there won't always be a session, eg rest api requests. You can get the most recently viewed one from user…
-
Current issue is available in the binding as issue. So to get the id you do issue.id.
-
The examples on your link are for groovy (script runner), rather than python (jira scripting suite). Either way, you will be wanting the javadoc for com.atlassian.jira.issue.link.IssueLinkManager and com.atlassian.jira.issue.CustomFieldManager.
-
But that seems like a valid answer ;-)
-
Please try not to "answer" a question with a comment, it just discourages people who may have answers from looking if there are already "answers". I converted it to a comment.
-
If you have an example that would probably be much appreciated by other people...!
-
Yeah, you need the !init bit, otherwise if all fields are present, it will commit the issue. It's fiddly, I went through this a while ago, but it should be possible.
-
You can, see http://confluence.atlassian.com/display/JIRA/Creating+Issues+via+direct+HTML+links.
-
Would be simple enough using a plugin, a script, or just a bunch of curl commands, however I think it would be better to pressure Atlassian into supporting a gravatar-like service JRA-24653, as Fisheye already does. Otherwise it's a constant pain to keep the pictures uptodate, and deal with the fact that users can upload…
-
The docn says to place it as the last function: https://jamieechlin.atlassian.net/wiki/display/GRV/Built-in%20Scripts#Built-InScripts-Fast-tracktransitionanissue
-
Isn't this the exact same question as https://answers.atlassian.com/questions/43113440
-
It's not hard with apache but the best solution is what you're most familiar with. Have you looked at http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+IIS ? For each app you need to change the context path, update the base url, change the proxyName and proxyPort in server.xml. For bonus points you should…
-
If the workflow action IDs are the same you can use the same escalation service. I think the question is more why do you want 50 different workflows. Anyway, say you have 50 genuinely different workflows, you can just write your own service rather than using the escalation service, which is just a shortcut. Anything you…