com.atlassian.greenhopper.service.issue

Interface IssueUpdateService

All Known Implementing Classes:

IssueUpdateServiceImpl

public interface IssueUpdateService

This is a work-around for deficiencies in JIRA's IssueService. It merely provides extra methods that are useful to GreenHopper, with a view that one day they will be ported over to JIRA.

Since:

v5.8.5

See Also:

IssueService

Method Summary

Modifier and Type	Method and Description
boolean	canEditField(com.atlassian.jira.issue.Issue issue, com.atlassian.jira.issue.fields.Field orderableField) Checks if field can be updated for the given issue.
com.atlassian.jira.bc.issue.IssueService.IssueResult	skipValidationAndUpdate(com.atlassian.jira.user.ApplicationUser user, Long issueId, com.atlassian.jira.issue.IssueInputParameters issueInputParameters) Skip validation checks and update issue.
com.atlassian.jira.bc.issue.IssueService.IssueResult	update(com.atlassian.jira.user.ApplicationUser user, com.atlassian.jira.bc.issue.IssueService.UpdateValidationResult updateValidationResult) Only here for convenience - don't actually do anything but delegate.
com.atlassian.jira.bc.issue.IssueService.UpdateValidationResult	validateUpdate(com.atlassian.jira.user.ApplicationUser user, Long issueId, com.atlassian.jira.issue.IssueInputParameters issueInputParameters) This needs to be promoted to JIRA!

Method Detail

validateUpdate

com.atlassian.jira.bc.issue.IssueService.UpdateValidationResult validateUpdate(com.atlassian.jira.user.ApplicationUser user,
                                                                               Long issueId,
                                                                               com.atlassian.jira.issue.IssueInputParameters issueInputParameters)

This needs to be promoted to JIRA! This implementation will always skip screen checks (we don't have this flag in IssueInputParameters yet) and will always retain existing issue values.

Parameters:

user -

issueId -

issueInputParameters -

Returns:

See Also:

com.atlassian.jira.bc.issue.IssueService#validateUpdate(User, Long, com.atlassian.jira.issue.IssueInputParameters)

update

com.atlassian.jira.bc.issue.IssueService.IssueResult update(com.atlassian.jira.user.ApplicationUser user,
                                                            com.atlassian.jira.bc.issue.IssueService.UpdateValidationResult updateValidationResult)

Only here for convenience - don't actually do anything but delegate.

Parameters:

user -

updateValidationResult -

Returns:

See Also:

IssueService#update(User, com.atlassian.jira.bc.issue.IssueService.UpdateValidationResult)

skipValidationAndUpdate

com.atlassian.jira.bc.issue.IssueService.IssueResult skipValidationAndUpdate(com.atlassian.jira.user.ApplicationUser user,
                                                                             Long issueId,
                                                                             com.atlassian.jira.issue.IssueInputParameters issueInputParameters)

Skip validation checks and update issue. This method is only to be used when updating the issue from within the JIRA system in certain cases, for example when the system needs to update a closed issue.

Parameters:

user -

issueId -

issueInputParameters -

Returns:

See Also:

IssueService#skipValidationAndUpdate(User, Long, com.atlassian.jira.issue.IssueInputParameters)

canEditField

boolean canEditField(com.atlassian.jira.issue.Issue issue,
                     com.atlassian.jira.issue.fields.Field orderableField)

Checks if field can be updated for the given issue.

Parameters:

issue - the issue on which depends what fields can be edited.

orderableField - the field to check

Returns:

true if field can be edited