Getting 'Invalid issue key provided:' error when executing test case

JIRA version - 5.1.8

Zephyr for Jira version - 1.6

We recently installed 'Zephyr for jira' plugin for evaluation and everything was going ok. However, now when i want to execute a test case from 'Test Cycle' tab or otherwise I get the following error message:

I've tried re-indexing & also restaretd the server to no avail..

Below is the log excerpt (search for ERROR) - it seems to be pointing at kepler plugin.

Log excerpt:

2013-02-19 15:31:53,108 http-8080-7 DEBUG aansari 931x1440x1 1hh0898 10.71.126.333 /rest/zephyr/latest/attachment/attachmentsByEntity [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,108 http-8080-7 DEBUG aansari 931x1440x1 1hh0898 10.71.126.333 /rest/zephyr/latest/attachment/attachmentsByEntity [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,108 http-8080-7 DEBUG aansari 931x1440x1 1hh0898 10.71.126.333 /rest/zephyr/latest/attachment/attachmentsByEntity [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/attachment/attachmentsByEntity

2013-02-19 15:31:53,108 http-8080-7 DEBUG aansari 931x1440x1 1hh0898 10.71.126.333 /rest/zephyr/latest/attachment/attachmentsByEntity [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/attachment/attachmentsByEntity

2013-02-19 15:31:53,110 http-8080-8 DEBUG aansari 931x1441x2 1hh0898 10.71.126.333 /rest/zephyr/latest/teststep/44475 [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,110 http-8080-8 DEBUG aansari 931x1441x2 1hh0898 10.71.126.333/rest/zephyr/latest/teststep/44475 [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,110 http-8080-8 DEBUG aansari 931x1441x2 1hh0898 10.71.126.333 /rest/zephyr/latest/teststep/44475 [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/teststep/44475

2013-02-19 15:31:53,110 http-8080-8 DEBUG aansari 931x1441x2 1hh0898 10.71.126.333 /rest/zephyr/latest/teststep/44475 [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/teststep/44475

2013-02-19 15:31:53,165 http-8080-7 DEBUG aansari 931x1443x1 1hh0898 10.71.126.333 /rest/keplerrominfo/jjupin/latest/lf/initPage [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,165 http-8080-7 DEBUG aansari 931x1443x1 1hh0898 10.71.126.333 /rest/keplerrominfo/jjupin/latest/lf/initPage [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,165 http-8080-7 DEBUG aansari 931x1443x1 1hh0898 10.71.126.333 /rest/keplerrominfo/jjupin/latest/lf/initPage [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/keplerrominfo/jjupin/latest/lf/initPage

2013-02-19 15:31:53,165 http-8080-7 DEBUG aansari 931x1443x1 1hh0898 10.71.126.333 /rest/keplerrominfo/jjupin/latest/lf/initPage [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/keplerrominfo/jjupin/latest/lf/initPage

2013-02-19 15:31:53,168 http-8080-7 ERROR aansari 931x1443x1 1hh0898 10.71.126.333 /rest/keplerrominfo/jjupin/latest/lf/initPage [jjupin.ui.livevalidator.LiveFieldRestService] Invalid issue key provided: Unscheduled

2013-02-19 15:31:53,177 http-8080-7 DEBUG aansari 931x1444x1 1hh0898 10.71.126.333 /rest/zephyr/latest/stepresult [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,177 http-8080-7 DEBUG aansari 931x1444x1 1hh0898 10.71.126.333 /rest/zephyr/latest/stepresult [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,178 http-8080-7 DEBUG aansari 931x1444x1 1hh0898 10.71.126.333 /rest/zephyr/latest/stepresult [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/stepresult

2013-02-19 15:31:53,178 http-8080-7 DEBUG aansari 931x1444x1 1hh0898 10.71.126.333 /rest/zephyr/latest/stepresult [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/stepresult

2013-02-19 15:31:53,201 http-8080-7 DEBUG aansari 931x1445x1 1hh0898 10.71.126.333 /rest/zephyr/latest/schedule/1/defects [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,201 http-8080-7 DEBUG aansari 931x1445x1 1hh0898 10.71.126.333 /rest/zephyr/latest/schedule/1/defects [plugins.rest.module.RestDelegatingServletFilter] Setting base uri for REST to 'latest'

2013-02-19 15:31:53,201 http-8080-7 DEBUG aansari 931x1445x1 1hh0898 10.71.126.333 /rest/zephyr/latest/schedule/1/defects [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/schedule/1/defects

2013-02-19 15:31:53,201 http-8080-7 DEBUG aansari 931x1445x1 1hh0898 10.71.126.333 /rest/zephyr/latest/schedule/1/defects [plugins.rest.module.RestDelegatingServletFilter] Incoming URI : /rest/zephyr/latest/schedule/1/defects

14 answers

1 accepted

This widget could not be displayed.

Hi Asif,

Indeed, looks like we assumed a CSS selector that was too generic. However, the error should be irrelevant in the Test Cycle tab. It should not interfere in any way with the page (other than just pop up). We'll look into this and fix it in time for our next release.

Regards,

Florin.

We identified the problem and are working on a fix. Looks like we were assuming that there is only one HTML tag with the id "key-val" and it contained the issue key, like it happens on any JIRA page, but the Execute Test page contains multiple tags with the same id.

<ul>
  <li><a id="key-val">...</a></li>
  <li><a id="key-val">...</a></li>
  <li><a id="key-val">...</a></li>
</ul>

A fix will be available with our next release.

We will contact you via email to resolve this ASAP.

Thanks Florin for the quick turnaround. When is the next anticipated release?

the snapshot build kepler provided has fixed the issue...thanks.

This widget could not be displayed.

Hi Asif,

Have you made any recent changes to your system, IE: installed plugins, permission changes, field changes, etc., that would have caused this issue to raise itself now after working fine for some time?

Additionally, can you provide a list of all your currently installed user plugins?

Regards,

Daniel

This widget could not be displayed.

Hi Daniel,

One thing that stands out in the plugin audit.log is:

Installed add-on JJupin (com.keplerrominfo.jira.plugins.jjupin version 2.5)

Installed add-ons katl-commons (com.keplerrominfo.jira.plugins.commons) - bundled with add-on jjupin

Thats what the log is pointing at also.

Thanks

Asif

This widget could not be displayed.

Some more useful information...

When I DISABLE the JJupin plugin the error mentioned above goes away.

This widget could not be displayed.

When you disable the JJupin the error goes away in the logs or are you able to execute in the cycle afterwards?

This widget could not be displayed.

I am able to execute in the cycle. We need a resolution pretty soon, as we are thinking off buying zephyr for jira. However both plugins (JJupin & zephyr) need to co-exist.

This widget could not be displayed.

I talked with one of our devs and it looks like the JJupin plugin plays a bit foul with our scheduling calls. We are looking into it. If you can send a full log to our support inbox, I can forward it on to our dev team to look at.

This widget could not be displayed.

Asif,

Our dev has replicated the issue and there is certainly a conflict between the two plugins. He will contact them directly.

This widget could not be displayed.

Hi,

Our dev has looked into this issue and found that it is indeed the JJupin add-on which is causing the error to appear. From our side, it looks like JJupin is assuming specific variables to be used for specific operations, which we are not using. This is an issue on JJupin's side. It is making assumptions on data which are not being met.

What needs to be done is, if you can, disable/skip JJupin for our execution screen and Test Cycle page. This will get rid of the error, which we have replicated and worked around in-house on our own machines.

Looking in longer terms, JJupin will need to change the way they assume information for other addons. You can do this by contacting the developer and letting them know what issue you are running into and additionally, what information we have given you on why it is happening.

Finally, we will be looking into changing some code on our side to help prevent JJupin's assumptions from interfering with our add-on functionality. However, no ETA can be made on these changes right now.

Regards,

Daniel

This widget could not be displayed.

How do I disable/skip JJupin for our execution screen and Test Cycle page?

This widget could not be displayed.

How do I disable/skip JJupin for our execution screen and Test Cycle page?

This widget could not be displayed.

Hi

Our team does not work with JJupin and has no experience with it. In order to get an answer for your question and if it is possible, you would need to contact the developer for that plugin. The issue being that it is active on Zephyr for JIRA-specific screens when it has no need to be.

I am willing to get on a call later this afternoon (PST) and do a quick talk about what we found and how it is affecting you and potential workarounds. If this is something you would like to do, please email support@getzephyr.com

We can further discuss it then.

Regards,

Daniel

This widget could not be displayed.

Danial,

As you can see from JJupin's teams comments below that they have identified the issue. However, as depicted below and I am sure there is a good reason for it, we were wondering why you have multiple DOM elements in your HTML?

This widget could not be displayed.

Hi,

We will be working on cleaning up our tags for our next release.

Suggest an answer

Log in or Sign up to answer
Atlassian Summit 2018

Meet the community IRL

Atlassian Summit is an excellent opportunity for in-person support, training, and networking.

Learn more
Community showcase
Posted Aug 06, 2018 in Jira Service Desk

A is for Activate: Share your top Jira Service Desk onboarding tips for new users!

Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :).  In the spirit of this month's  august-challenge, we're sourcing stories of Jira Service Desk activation fro...

551 views 25 15
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you