Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

r4j coverage view not loading after upgrade to 4.0.2


Has anyone else seen any issues after upgrading from 3.x to 4.x?

Only some of our coverage views are loading, but they are loading much more slowly than before.  Some of the others cause my browser to go "Aww, snap."

The data set is quite large, but it used to load without any issues before.  I'd like to get that functionality back as teams rely on it to do their breakdowns.

Please help.


2 answers

1 accepted

0 votes
Answer accepted

To anyone still having this issue, you can downgrade back to 3.5.4.  This is what we ended up doing in our instance.

Below is a quote regarding my ticket with Ease Solutions:

We’ve had our testers confirm this and so far the only issue you should have is that the new views you created after migrating to 4.x will not be available when downgrading; And updates from migrated views will not reflect as well.

This is assuming that you did not do any manual data alterations in the database. Switching back to a lower version than 4.x means that the old tables and data will be used for all views fetched/saved/deleted. You’re going back to a state before any migration was done.

As always, before you do any update we recommend to keep a backup of your data.

We have the same problem. Since the update to 4.0.2 our personal and public views have disappeared and Coverage gives 'Request Failed'. I am very interested in finding out a work-around or solution to this problem! 



Hi Mathijs,

As for the views, you should do the migration described here:

But as for the "Request Failed", I find that ours is intermittent - when JIRA is busy, it doesn't complete, but if there is not a lot of load on the system, it works fine, albeit slow.

If there's anyone from Ease Solutions who can comment, that would be great.



Like Angelica Salazar likes this

Suggest an answer

Log in or Sign up to answer

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you