[#JRA-8794] Unable to CreateIssue or Comment as another user via SOAP (eg. set reporter)

JIRA

Unable to CreateIssue or Comment as another user via SOAP (eg. set reporter)

Created: 13/Dec/05 07:48 PM Updated: 15/Jan/07 10:44 PM

Component/s:

Remote API (SOAP & XML-RPC)

Affects Version/s:

3.4.1

Fix Version/s:

3.6.3

Time Tracking:

Not Specified

File Attachments:

atlassian-jira-rpc-plugin-3.5.2-1.jar (101 kB)
2.

atlassian-jira-rpc-plugin-3.6-1.jar (101 kB)
3.

atlassian-jira-rpc-plugin-3.6.5-1_JRA-8794.jar (105 kB)
4.

IssueServiceImpl.class (28 kB)

Issue Links:

Reference

This issue relates to:

JRA-8791 Remote API has useless setters on the Remote Objects

Participants:	Dushan Hanuska [Atlassian], Gerd Gueldenast, Justin Koke [Atlassian], Kyle Saugier and Sean Rees
Since last comment:	2 years, 17 weeks, 5 days ago
Resolution Date:	01/Aug/06 12:03 AM
Labels:

Description

« Hide

When logged in using a user with Create Issue/Assign Issue/Modify Reporter via SOAP both CreateIssue and AddComment create as the logged inuser regardless of what is set in the Remote Objects being submitted.

If a user has Modify Reporter the Issue/Comment should be created with the specified data rather than current user data.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Gerd Gueldenast added a comment - 05/Apr/06 01:18 AM

We really want to use this feature. When you schedule Release 3.7. could you please correct this bug?

[ Permlink | « Hide ]

Justin Koke [Atlassian] added a comment - 10/Apr/06 01:03 AM

The attached class file will allow you to set the reporter of the issue via SOAP.

If the reporter is not set on the remote issue the user that is used to create the issue will be used as the reporter.

Regards,
Justin

[ Permlink | « Hide ]

Justin Koke [Atlassian] added a comment - 25/Apr/06 11:18 PM

The attached jar file is a point release of 3.6 that will allow for the setting of the reporter.

If this fails to work, please post a comment to this issue.

[ Permlink | « Hide ]

Gerd Gueldenast added a comment - 03/May/06 03:16 AM

I can confirm, that the fix works very well with version 3.5.2. Thanks for the resolution, Justin.

[ Permlink | « Hide ]

Gerd Gueldenast added a comment - 30/May/06 04:05 AM

Also works well with 3.6.1 and 3.6.2.

When will this bugfix be officialle incorpoated into one of the JIRA Releases? Maybe 3.6.3 ?

[ Permlink | « Hide ]

Sean Rees added a comment - 08/Jun/06 07:05 PM

Can you attach the source file?

[ Permlink | « Hide ]

Dushan Hanuska [Atlassian] added a comment - 12/Jun/06 09:32 PM

The few lines in question that allow you to set the reporter for an issue are the following:

This is added to the: private Map makeActionParams(final GenericValue project, RemoteIssue rIssue, User user) throws RemoteValidationException of the IssueServiceImpl class

if(StringUtils.isNotEmpty(rIssue.getReporter()))
{
    actionParams.put(IssueFieldConstants.REPORTER, new String[]{rIssue.getReporter()});
}
else
{
    actionParams.put(IssueFieldConstants.REPORTER, new String[]{user.getName()});
}

// in replace of:
// actionParams.put(IssueFieldConstants.REPORTER, new String[]{user.getName()});