Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
  • Community
  • Q&A
  • Jira
  • Questions
  • Subversion tabpanel breaks with following message. "Error rendering com.atlassian.jira.plugin.ext.subversion:subversion-commits-tabpanel. Please contact your JIRA administrators".

Complete sprint shows 0 completed issues

James Orola
Contributor
December 15, 2019

I have only the default 3 columns and 3 statuses: TODO, IN PROGRESS, DONE

There are 2 issues in TODO, 4 in IN PROGRESS and the rest is in DONE which is also the last column in the sprint board. However when I try to complete the sprint it is always showing me 0 completed issues and that I need to move all issues into the next sprint or backlog. Obviously this is not true because there are 20+ issues already in DONE column / status.

Note that we have also enabled story points but not logging any work done. It was only to aid us in estimating the tasks to be added in the sprint. I have already tried removing the value for one of the DONE tasks but it didn't made a difference.

Now at lost on how to fix this issue. I have read from other questions that the basic reason is the matching the done status with the last column in the board, but this is already the case for us. There also doesn't seem to be a way to customize the workflow in a next-gen project so we should not run into status mapping issue. Anything else I am missing here?

2 answers

0 votes
pschaff01
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 7, 2014

Hi David,

As it turns out, I believe you are actually facing a bug with SVN that is being tracked here:

https://ecosystem.atlassian.net/browse/SVN-364

Some customers mentioned that a restart of the JIRA application resolved the issue, but this is not a confirmed workaround.

Cheers

0 votes
Janet Albion
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
January 17, 2013

Hi David,

There are various of reason why the error will be thrown. Perhaps checking the Caused by for the trace will give better idea.

For detail logging, you might want to enable the Debug logging for the SVN plugin. Check if the repository is too large, is it always stuck at the same revision number, check if it is really network timeout. By the way, what Subversion version this JIRA connecting to ?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events