Your browser was unable to load all of the resources. They may have been blocked by your firewall, proxy or browser configuration.
Press Ctrl+F5 or Ctrl+Shift+R to have your browser try again.

JIRA integration #1327

milan.rusek ·
Hi, we would like to integrate QB with JIRA but we can not set duedate for new issues. Do you know anybody how can we do it? <!-- s:? --><img src="{SMILIES_PATH}/icon_confused.gif" alt=":?" title="Confused" /><!-- s:? -->

Thank you
Milan
  • replies 13
  • views 5543
  • stars 0
robinshen ADMIN ·
Hi Milan,

Do you mean that once the QB plugin for JIRA is installed, the new issues created in JIRA will not able to set due date? Or do you mean issues created via QB step can not set the due date field?

Regards
Robin
milan.rusek ·
Hi Robin,

I mean that issues created via QB step "Create JIRA Issues" can not set the due date field by extra attributes. The duedate is not presented in SOAP message for JIRA. I have tested various datetime formats but neither one has accepted. Could you sent me any idea how can I do it?

Thank you
Milan
robinshen ADMIN ·
Hi Milan,

I've filed this as a bug: http://track.pmease.com/browse/QB-824

Please watch on this issue to get notified once it is resolved.

Regards
Robin
milan.rusek ·
Hi Robin,

I have analyzed this issue and I found duedate attribute in SOAP request but it has been set at NULL value whenever.

Thank you,
Milan
robinshen ADMIN ·
Hi Milan,

Thanks for the investigation. We've solved the issue and will come up with a patch release in one or two days.

Regards
Robin
milan.rusek ·
Hi Robin,

Creating JIRA issue still does not work. The following message occurs in build log:

01:46:57,998 [master>Create JIRA issue@czpra775:443] ERROR - Step 'master>Create JIRA issue' is failed.
com.pmease.quickbuild.plugin.tracker.core.TrackerException: com.atlassian.jira.rpc.exception.RemoteValidationException: {duedate=Due Date is required.} : []
at com.pmease.quickbuild.plugin.tracker.jira.client.JiraClient.createIssue(JiraClient.java:515)
at com.pmease.quickbuild.plugin.tracker.jira.step.CreateIssueStep.run(CreateIssueStep.java:242)
at com.pmease.quickbuild.plugin.tracker.jira.step.CreateIssueStep$$EnhancerByCGLIB$$3890a533.CGLIB$run$0(<generated>)
at com.pmease.quickbuild.plugin.tracker.jira.step.CreateIssueStep$$EnhancerByCGLIB$$3890a533$$FastClassByCGLIB$$77313f89.invoke(<generated>)
at net.sf.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:215)
at com.pmease.quickbuild.DefaultScriptEngine$Interpolator.intercept(DefaultScriptEngine.java:273)
at com.pmease.quickbuild.plugin.tracker.jira.step.CreateIssueStep$$EnhancerByCGLIB$$3890a533.run(<generated>)
at com.pmease.quickbuild.stepsupport.Step.execute(Step.java:442)
at com.pmease.quickbuild.stepsupport.StepJob.execute(StepJob.java:42)
at com.pmease.quickbuild.grid.GridJob.run(GridJob.java:122)
at java.lang.Thread.run(Unknown Source)
Caused by: com.atlassian.jira.rpc.exception.RemoteValidationException: {duedate=Due Date is required.} : []
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Source)
at java.lang.reflect.Constructor.newInstance(Unknown Source)
at java.lang.Class.newInstance0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:104)
at org.apache.axis.encoding.ser.BeanDeserializer.<init>(BeanDeserializer.java:90)
at com.dolby.jira.net.soap.jira.RemoteValidationException.getDeserializer(RemoteValidationException.java:75)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getSpecialized(BaseDeserializerFactory.java:154)
at org.apache.axis.encoding.ser.BaseDeserializerFactory.getDeserializerAs(BaseDeserializerFactory.java:84)
at org.apache.axis.encoding.DeserializationContext.getDeserializer(DeserializationContext.java:464)
at org.apache.axis.encoding.DeserializationContext.getDeserializerForType(DeserializationContext.java:547)
at org.apache.axis.message.SOAPFaultDetailsBuilder.onStartChild(SOAPFaultDetailsBuilder.java:157)
at org.apache.axis.encoding.DeserializationContext.startElement(DeserializationContext.java:1035)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractXMLDocumentParser.emptyElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at javax.xml.parsers.SAXParser.parse(Unknown Source)
at org.apache.axis.encoding.DeserializationContext.parse(DeserializationContext.java:227)
at org.apache.axis.SOAPPart.getAsSOAPEnvelope(SOAPPart.java:696)
at org.apache.axis.Message.getSOAPEnvelope(Message.java:435)
at org.apache.axis.handlers.soap.MustUnderstandChecker.invoke(MustUnderstandChecker.java:62)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:206)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at com.dolby.jira.net.soap.jira.JirasoapserviceV2SoapBindingStub.createIssue(JirasoapserviceV2SoapBindingStub.java:3790)
at com.pmease.quickbuild.plugin.tracker.jira.client.JiraClient.createIssue(JiraClient.java:507)
... 10 more


See following image for Create JIRA issue step configuration:
http://www.rusek.cz/CreateIssueBug.GIF

We are using QB

System Date and Time 2011-05-10 10:48:13
Operating System Windows XP 5.1, x86
JVM Java HotSpot(TM) Client VM 19.1-b02, Sun Microsystems Inc.
QuickBuild Version 3.1.38 - Sun May 01 03:21:38 CEST 2011
Total Heap Memory 989 MB
Used Heap Memory 125 MB
Heap Memory Usage 12%
OS User Name SYSTEM

BR,
Milan
steveluo ADMIN ·
Hi Milan,
Please change your setting as below:

duedate=${util.formatDate(build.getBeginDate())}
dateformat=yyyy-MM-dd HH:mm:ss


The dateformat is the pattern for duedate.
milan.rusek ·
Hi,

thank you, now it works well! <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) -->

Milan
milan.rusek ·
Hi,

I would like to access to "Associated Project Key" option from JIRA server settings in mvel script. How can I do it?


import com.pmease.quickbuild.plugin.tracker.jira.client.JiraClient;
import com.dolby.jira.net.soap.jira.RemoteVersion;

if (system.getPlugin("jira").isEnabled())
{
JiraClient client = JiraClient.newInstance();
RemoteVersion[] s = client.getVersions("<Here I would like to call the getter ...>");
// ... some actions for versions
}


Best Regards,
Milan
steveluo ADMIN ·
Please try:


import com.pmease.quickbuild.plugin.tracker.jira.setting.JiraSetting;

JiraSetting setting = JiraSetting.get(configuration);
logger.info("Associated project is: " + setting.getAssociatedProject());
milan.rusek ·
Thank you, It works! <!-- s:D --><img src="{SMILIES_PATH}/icon_biggrin.gif" alt=":D" title="Very Happy" /><!-- s:D -->

Best Regards,
Milan
michael1 ·
Does anyone know if it's possible or come up with a way to integrate JIRA properly with Confluence? Out goal is to provide a 'customer portal' using Confluence but one of the things that would be a requirement to make sure the project is a success would be to allow our users to create issues from the portal.

I've read about people using the JIRA portlet to create almost like executive dashboards inside Confluence but I'm surprised that I haven't come across anyone wanting to create & manage issues as well.

Any thoughts or suggestions would be much appreciated!

Regards,
Michael
robinshen ADMIN ·
[quote="michael1"]Does anyone know if it's possible or come up with a way to integrate JIRA properly with Confluence? Out goal is to provide a 'customer portal' using Confluence but one of the things that would be a requirement to make sure the project is a success would be to allow our users to create issues from the portal.

I've read about people using the JIRA portlet to create almost like executive dashboards inside Confluence but I'm surprised that I haven't come across anyone wanting to create & manage issues as well.

Any thoughts or suggestions would be much appreciated!

Regards,
Michael[/quote]
I guess this problem should be posted to atlassian product forum instead (<!-- w --><a class="postlink" href="http://www.atlassian.com">www.atlassian.com</a><!-- w -->)