Issue Details (XML | Word | Printable)

Key: JRA-10341
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Dylan Etkin [Atlassian]
Reporter: Sean Rees
Votes: 1
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
JIRA

Adding New Version does not show up in Open Issues or via SOAP until Restart

Created: 02/Jun/06 11:43 AM   Updated: 10/Aug/06 12:18 AM
Component/s: Administration
Affects Version/s: 3.6
Fix Version/s: 3.6.3

Time Tracking:
Not Specified

Environment: Linux 2.6.9 (RHEL), Tomcat 5.5.15, JREK 1.5.0_06, JIRA 3.6 Enterprise
Issue Links:
Duplicate
 
Reference

Participants: Chris Mountford [Atlassian], Dylan Etkin [Atlassian], Scott Farquhar [Atlassian] and Sean Rees
Since last comment: 2 years, 8 weeks, 3 days ago
Resolution Date: 10/Aug/06 12:18 AM
Labels:


 Description  « Hide
Adding a new version to a project does not show up in the Open Issues in 'Browse Project' or via a getVersions call over SOAP until JIRA is restarted. However, the new version does show up on the road map and issues can be placed in the new version.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Sean Rees added a comment - 02/Jun/06 11:44 AM
This issue could also be related to JRA-10272.

Scott Farquhar [Atlassian] added a comment - 02/Jun/06 11:27 PM
Sean,

If you add a version - it won't turn up in open issues, unless it has issues assigned to it. Is that your case?

If so - does is it just a soap problem? Did you do an import at all?


Sean Rees added a comment - 05/Jun/06 09:38 AM
Not my case, no. I did add a few (2) issues to this new version.

This was my procedure:

1) Add a version to the project.
2) This new version shows up on the Road Map and in the Fix For list.
3) I assigned a few issues into it.
4) I tried getting a list of versions for the project (getVersions() over SOAP) and it turned up all the versions except my new one.
5) Version did not show on Open Issues, despite having issues in it.

Hope that helps.


Chris Mountford [Atlassian] added a comment - 07/Jun/06 08:22 PM
I've confirmed this. From my testing this problem seems to be reproducible after having restored from backup.

As with JRA-10272 the restore from backup leaves some things out of date. the Open Issues project tab and the SOAP client are now both confirmed. Roadmap seems to have been refreshed properly.


Dylan Etkin [Atlassian] added a comment - 10/Aug/06 12:18 AM
This was resolved in the 3.6.3 release. The problem was that the managers that the axis servlet were holding onto were stale once an import occurred. We now have a bit of trickery so that we refresh the entire graph held by the axis servlet so we will not run into these "out-of-sync" issues any longer.