JamieA Expert

Can you use the CODE formatting on the toolbar, it's not possible to read that.

You're probably treating them as strings or something, use parseInt()

This can't be related to the javascript you added...

No worries... feel free to mark my answer as correct / vote it up / both ;-)

When an issue is created it displays a link to the issue. Would probably be better if you removed that, and just replaced with a "thanks for giving feedback" type message.

I'm sure that would be fine, if you specify in the issue collector that the reporter is a always the same user. One other thing that I consider a potential security issue, is that the issue collector allows matching an email address provided with a jira user, and then entering the issue as that user. I think this is a bit…

It is a big deal and I think you're right to be worrying about it. I'm not sure there are any shortcuts... although there are plenty of public jira instances out there, but you will need to be careful about patching, making sure anonymous access is denied etc. Also don't forget the issue collector is "beta" - you would not…

Yeah... also take into account a lot of the online documentation won't make sense to the users. In fact, just say no. People will get used to the jira way in no time at all.

Yes, you can change the "issue.field.reporter" etc property in the language file... have a look at http://confluence.atlassian.com/display/JIRA/Translating+JIRA for details of how to do it.

I just tested this on JIRA 6.4.1 and it worked fine... can you paste the following code in to the script console and run it: import com.atlassian.jira.component.ComponentAccessorimport com.atlassian.jira.security.roles.ProjectRoleManagerdef projectRoleManager =…

looks like it can't find that role - is it still valid?

The previous line should be an exception - can you post that as well?

Can you now turn this off by default? Related question: https://answers.atlassian.com/questions/54126/can-jira-s-autowatch-be-disabled

The spam seems to be getting worse... the spam filter I guess is not working too well. At a first step could we at least be allowed to delete questions, and without 5 confirmation boxes either.

> CustomField 'Custom Field' = customFieldManager.getCustomFieldObjectByName( "Custom Field" ); This is not valid... you are trying to use 'Cust Field' as a variable name.Just do:def customField = customFieldManager.getCustomFieldObjectByName( "Custom Field" );Add some log.warn (...) lines and check the log.Doing a quick…

try http://stackoverflow.com/questions/290254/how-to-order-events-bound-with-jquery or http://stackoverflow.com/questions/827107/jquery-mulitple-click-handlers-how-to-ensure-order-of-firing. You might be better off just making a source hack though. Also yeah, the iframe may change things, not sure...

Ah yes, sounds like another dom ready handler is also setting focus. BTW I tried it on an older version, 3.4.9, maybe it's changed. You could try AJS.toInit(..) instead of AJS.$(). It's also possible with some javascript to make your handler fire last, but it's a bit of a pain...

I just pasted it into the Chrome console... press f12. Or same in firefox with firebug...

Worked for me (tm). Is the JS definitely running? Try an alert or console.log statement,

You need to put something on jira's mail queue or invoke the send method from the mail server. def mailServerManager = componentManager.getMailServerManager() def mailServer = mailServerManager.getDefaultSMTPMailServer() SingleMailQueueItem item = new SingleMailQueueItem(email); ManagerFactory.getMailQueue().addItem(item);…

You need to put a listener on the subtask type, or on the subtask workflow at whatever point "Complete" is. Then just check the summary for your special string, if it matches, create more subtasks. > Also, how to make the options chosen from the customer channel form as triggers to create specific subtasks? Not sure what…

Can you post the behaviours script that you are using? I think this thing about the admin user might be a red herring, I can't see how this could make a difference...

A stack trace is helpful, but if I knew the version of the plugin it would be much more helpful, as then I could tally the line numbers with the code. Seems to be something to do with a cascading select. Does any of your behaviour scripts deal with cascading selects? Have options been removed or renamed recently, or the…

did you publish the workflow? If you did, try putting that just before step 5.

can you give details - what's in the logs?

you can just paste it in to the script field.

something like: if (issue.summary.contains("site catalyst")) { issue.setAssigneeId("someuser")} if you have that as the first post-function it should work.

From the list of custom fields, click Edit.

No.

Agree with Nic. People seem to be using this exactly as the old forums. Some users are definitely not clued up for this either.