When will Zephyr fix compatibility issue with JIRA 6.3.10?

We upgraded to JIRA 6.3.10 yeserday and according to the compatibility check Zephyr was compatible. It turned out that it wasn't and we are very anxios to know when Zephyr will release a new compatible version!

8 answers

What type of issues are you having? We are having issues with Zephyr and JIRA 6.3.9 where test executions that already existed won't display now after the upgrade.

We cannot start Zephyr at all. The plugin is disabled .with the status : INCOMPATIBLE - -UPDATE REQUESTED . Note taht we upgraded to JIAR 6.3.10


we also purchased Zephyr and I specifically just upgraded our complete tool suite to be able to integrate Zephyr. Since I naturally installed the current version of JIRA, I installed 6.3.10. And this is currently not supported by zephyr.

Since there is no way to downgrade, I am stuck. We bought Zephyr for a lot of money, and I like to use this now. How long am I supposed to wait?

Hello Everyone,

We at Zephyr just wanted to reach out and say that creating a compatible version of Zephyr for JIRA for JIRA 6.3.10 is currently our top priority. We are glad to say that we are working on finalizing a release for this issue and project a public release in two weeks.



Any ETA on this as we are awaiting to upgrade and this is holding us back?

Same here. Any ETA for the update?

An updated version is out now. Please see my post below for details.

We are having the same issue.  This is a huge issue for us and if you can provide a timeline or even a beta version so that we can get this to work that would be great.

We have upgraded to 6.3.10 and this has become a huge issue for us. Do we have a status update to see when we might have it released?

We hit the same issue when we upgraded to 6.3.10 (and 6.3.11)

Zephyr's atlassian-plugin.xml file references the following condition: com.atlassian.jira.plugin.webfragment.conditions.CanAttachScreenshotToIssueCondition

which does not appear to exist in JIRA as of 6.3.10. However, the following condition does: com.atlassian.jira.plugin.webfragment.conditions.CanAttachFileToIssueCondition

We simply unpacked the .obr and .jar file and changed the file to reference the other condition. My assumption is that Screenshots are simply considered Files now and do not have a dedicated condition. We have been using Zephyr with this fix for weeks with no issue.

EDIT: Here is our patched copy for anyone not familiar with unpacking and repacking plugins:

Hello Everyone,

Zephyr just went live with Zephyr for JIRA 2.5.2. This version includes bug fixes and most importantly - comparability with JIRA 6.3.10 and 6.3.11. Users can upgrade either via the UPM or downloading from our Marketplace page linked below:


Important: After performing a normal upgrade, please first re-index JIRA and then re-index Zephyr for JIRA in order to start seeing your data again.

Please view our Knowledge Base article on the issue linked below for more information:


Kind Regards, 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

866 views 3 9
Read article

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