[#JRA-9418] setArchived and setReleased in RemoteVersion does nothing

JIRA

setArchived and setReleased in RemoteVersion does nothing

Created: 22/Feb/06 01:10 AM Updated: 04/Sep/06 06:37 PM

Component/s:

Remote API (SOAP & XML-RPC)

Affects Version/s:

3.5.1

Fix Version/s:

3.6.4

Time Tracking:

Not Specified

Participants:	Justin Koke [Atlassian], Mark Chaimungkalanont [Atlassian], Scott Farquhar [Atlassian] and Steven Swart
Since last comment:	2 years, 9 weeks, 6 days ago
Resolution Date:	08/Aug/06 12:10 AM
Labels:

Description

« Hide

setArchived and setReleased in RemoteVersion does nothing in SOAP RPC.

It should release or archive a version if this is set

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Scott Farquhar [Atlassian] added a comment - 01/Aug/06 12:08 AM

We should fix this, or if it is more than 2 hours to fix - we should remove these methods, and then raise an improvement request.

[ Permlink | « Hide ]

Steven Swart added a comment - 02/Aug/06 05:49 AM

While dealing with this issue, it might also be beneficial to check the setReleaseDate() method.

BTW: We've been waiting for a fix ever since I reported this issue on the forums. Please fix it!

[ Permlink | « Hide ]

Justin Koke [Atlassian] added a comment - 07/Aug/06 12:36 AM

I can verify that the boolean flags for released and archive do not work.

Steven, testing the setReleasedDate() did work, using code like the following:

final RemoteVersion version = new RemoteVersion();
        version.setName("3 SOAP created version " + new Date());
        version.setSequence(new Long(6));
        version.setReleased(true);
        version.setReleaseDate(Calendar.getInstance());
        final RemoteVersion createdVersion = jiraSoapService.addVersion(token, ClientConstants.PROJECT_KEY, version);

[ Permlink | « Hide ]

Steven Swart added a comment - 07/Aug/06 12:43 AM

That's fine, but I would need to set a Release Date on an already existing version. Not sure how to do this...

[ Permlink | « Hide ]

Justin Koke [Atlassian] added a comment - 08/Aug/06 12:05 AM

Hi Steven,

I have added the following functionality to JIRA's RPC plugin:

For releasing a Project Version, set the release flag (true or false), and set the release date.

final RemoteVersion version = new RemoteVersion();
        version.setName("Test Version Name");
        version.setReleased(true);

        Calendar releaseDate = Calendar.getInstance();
        releaseDate.set(Calendar.MONTH, Calendar.DECEMBER);
        releaseDate.set(Calendar.YEAR, 2006);
        releaseDate.set(Calendar.DATE, 25);
        version.setReleaseDate(releaseDate);

        jiraSoapService.releaseVersion(token, projectKey, version);

For archiving, specify the version name, project key and true or false if you wish to archive/un-archive a version:

jiraSoapService.archiveVersion(token, projectKey, versionName, true);

This functionality will be available in JIRA 3.6.4 and I hope it will meet your needs.

Regards,
Justin

[ Permlink | « Hide ]

Justin Koke [Atlassian] added a comment - 08/Aug/06 12:10 AM

funtionality has been added to the create to handle setting if a version is release or archived. And methods have been add to toogle versions from being released or archived.

[ Permlink | « Hide ]

Steven Swart added a comment - 08/Aug/06 02:44 AM

Hi Justin

Thanks a lot, we have been waiting for this fix for a while now, reason being, we have the same versioning system across multiple projects, and I have developed a soap service command-line tool that updates versions across all our projects at the same time, which is painful to do manually.

I am eagerly anticipating 3.6.4, for this and because it also has a fix that workflow updates no longer change the 'Updated' settings for all issues, something that causes us a few headaches.

Thanks again,
S.