java.lang.Object | |
↳ | com.atlassian.jira.issue.managers.DefaultIssueManager |
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Public method used internally, not safe to override.
| |||||||||||
This method is here because this is a logical place for the "createIssue" method to be.
| |||||||||||
This function creates an issue in Jira.
| |||||||||||
Persists a new issue.
| |||||||||||
Creates an issue.
| |||||||||||
Creates an issue.
| |||||||||||
Creates an issue.
| |||||||||||
This method will delete an issue from JIRA.
| |||||||||||
This method will delete an issue from JIRA.
| |||||||||||
Delete issue without firing any events, or sending notifications.
| |||||||||||
Delete issue without firing any events, or sending notifications.
| |||||||||||
Returns an issue that has been moved by searching on the old issue key.
| |||||||||||
Returns all issue keys that are associated with
Issue . | |||||||||||
Get a list of entities (versions, components etc) related to this issue.
| |||||||||||
Get a list of entities (versions, components etc) related to this issue.
| |||||||||||
Check existence of issues for the given set of IDs
| |||||||||||
Retrieves the issue as a GenericValue with the given key.
| |||||||||||
Retrieves an issue by its id.
| |||||||||||
Retrieves the
Issue that has the given key, or null if no such Issue exists. | |||||||||||
Retrieves the
Issue that has the given key, or null if no such Issue exists. | |||||||||||
Retrieves an issue GenericValue given a workflow ID.
| |||||||||||
Returns the number of issues.
| |||||||||||
Returns the number of issues that exist for the provided project id.
| |||||||||||
Retrieve a collection of all issue ids that belong to a given project.
| |||||||||||
Retrieves the
Issue that has the given key, or null if no such Issue exists. | |||||||||||
Retrieves an issue by id.
| |||||||||||
Retrieves an issue given a workflow ID.
| |||||||||||
Get issues with the following ids.
| |||||||||||
Get a list of issues related to an entity (version, component etc).
| |||||||||||
Get issues with the following ids.
| |||||||||||
Get a list of issues related to an entity (version, component etc).
| |||||||||||
Check existence of issues for the given set of keys
| |||||||||||
Returns a set of project ID / issue type combinations that given issue IDs cover.
| |||||||||||
Returns a set of project ID / issue type combinations that given issue keys cover.
| |||||||||||
Get all the issues for a given project.
| |||||||||||
Returns the number of unassigned issues.
| |||||||||||
Get a list of issues that the user has voted on and can see.
| |||||||||||
Get a list of issues that the user has voted on.
| |||||||||||
Get a list of issues that the user is watching and can see.
| |||||||||||
Get a list of issues that the user is watching
| |||||||||||
Return a list of watchers for a particular issue.
| |||||||||||
Return a list of watchers for a particular issue.
| |||||||||||
Returns a boolean indicating whether there are unassigned issues.
| |||||||||||
Returns
true if the issue can be edited by the current user. | |||||||||||
Returns
true if the issue can be edited. | |||||||||||
Returns true if issue with a given key exists (it looks for issues having current issue key set for the value,
and moved issue keys that used the key).
| |||||||||||
Used internally when we want to record that an Issue has changed its Issue key (because it has moved project).
| |||||||||||
This method will store the provided issue to the JIRA datastore.
| |||||||||||
This method will store the provided issue to the JIRA datastore.
|
Protected Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Creates a MutableIssue object from an Issue GenericValue.
| |||||||||||
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
![]() | |||||||||||
![]() |
Public method used internally, not safe to override.
This method is here because this is a logical place for the "createIssue" method to be. As the issues are
actually created using workflow, the current implementation of this method uses the WorkflowManager
to create the issue
remoteUserName | the user who is creating the issue |
---|---|
fields | issue attributes |
CreateException |
---|
This function creates an issue in Jira. Read the javadoc under the fields parameter to see what object need to be passed to create an issue.
remoteUser | User that is creating this issue |
---|---|
fields | see below
Required FieldsprojectId: A Long value representing the id of the projectissueType: The String id of an issueType summary: A String describing the issue (max 255 chars) Recomended Fieldsassignee: A String representing the username of the assigneereporter: A String representing the username of the reporter priority: The String id of a priority Optional Fieldsdescription: A String description of the issueenvironment: A String description of the environment the issue is in. e.g W2K fixVersions: A List of Long values representing fixVersion ids components: A List of Long values representing component ids timeOriginalEstimate: A Long value representing the number of seconds this tast should take timeEstimate: A Long value representing the number of seconds allocated for this issue versions: = A List of Long value representing version ids customFields: A Map with the CustomField as the key and Transport Object of the CF as the value created: The date which the issue was created. If not specified, defaults to currentTimeMillis() updated: The date which the issue was updated. If not specified, defaults to currentTimeMillis() |
CreateException | |
CreateException |
Persists a new issue.
remoteUser | Issue creator |
---|---|
issue | The new issue. |
CreateException |
---|
Creates an issue.
remoteUser | Issue creator |
---|---|
issue | The new issue. |
CreateException |
---|
Creates an issue.
remoteUser | Issue creator |
---|---|
fields | A map of the issue's immediate field values. See the Issue definition in entitymodel.xml for values. |
CreateException |
---|
Creates an issue.
remoteUserName | Issue creator |
---|---|
fields | A map of the issue's immediate field values. See the Issue definition in entitymodel.xml for values. |
CreateException |
---|
This method will delete an issue from JIRA.
This will clean up all issue associations in JIRA and will de-index the issue.
This method should be used if you want to exert more control over what happens when JIRA deletes an issue. This
method will allow you to specify if an event is dispatched and if so which event is dispatched, see
EventDispatchOption
. This method also allows you to specify if email
notifications should be send to notify users of the deletion.
user | who is performing the operation |
---|---|
issue | the issue to delete. |
eventDispatchOption | specifies if an event should be sent and if so which should be sent. |
sendMail | if true mail notifications will be sent, otherwise mail notifications will be suppressed. |
RemoveException |
---|
This method will delete an issue from JIRA. This will clean up all issue associations in JIRA and will de-index the issue.
This method should be used if you want to exert more control over what happens when JIRA deletes an issue. This
method will allow you to specify if an event is dispatched and if so which event is dispatched, see
EventDispatchOption
. This method also allows you to specify if email
notifications should be send to notify users of the deletion.
user | who is performing the operation |
---|---|
issue | the issue to delete. |
eventDispatchOption | specifies if an event should be sent and if so which should be sent. |
sendMail | if true mail notifications will be sent, otherwise mail notifications will be suppressed. |
RemoveException |
---|
Delete issue without firing any events, or sending notifications.
This is preferred in some bulk operations, but normally you would call #deleteIssue(com.atlassian.crowd.embedded.api.User, MutableIssue, com.atlassian.jira.event.type.EventDispatchOption, boolean)
issue | issue to delete |
---|
RemoveException |
---|
Delete issue without firing any events, or sending notifications.
This is preferred in some bulk operations, but normally you would call #deleteIssue(com.atlassian.crowd.embedded.api.User, Issue, com.atlassian.jira.event.type.EventDispatchOption, boolean)
issue | issue to delete |
---|
RemoveException |
---|
Returns an issue that has been moved by searching on the old issue key.
originalKey | the original key of an issue that has since been moved (moving between projects assigns a new key to an issue) |
---|
Issue
object
Returns all issue keys that are associated with Issue
.
Get a list of entities (versions, components etc) related to this issue.
relationName | A IssueRelationConstants string indicating some issue relation |
---|---|
issue | Issue to consider |
GenericEntityException |
---|
Get a list of entities (versions, components etc) related to this issue.
relationName | A IssueRelationConstants string indicating some issue relation |
---|---|
issue | Issue to consider |
GenericEntityException |
---|
Check existence of issues for the given set of IDs
issueIds | Set of issue IDs |
---|
Retrieves the issue as a GenericValue with the given key.
key | the issue key. |
---|
GenericEntityException |
---|
Retrieves an issue by its id.
id | Issue ID. |
---|
DataAccessException |
---|
Retrieves the Issue
that has the given key, or null if no such Issue exists.
This method will strictly only return the issue which has current issue key equal to the one given.
key | The Issue key. |
---|
MutableIssue
with the given key, or null if no such Issue exists.DataAccessException |
---|
Retrieves the Issue
that has the given key, or null if no such Issue exists.
This method will ignore case of issue key.
key | The Issue key. |
---|
MutableIssue
with the given key, or null if no such Issue exists.DataAccessException |
---|
Retrieves an issue GenericValue given a workflow ID. This is used when transitioning through the various steps of a workflow.
wfid | workflow ID. |
---|
GenericEntityException |
---|
Returns the number of issues.
Returns the number of issues that exist for the provided project id.
projectId | identifies the project which the issues are associated with |
---|
Retrieve a collection of all issue ids that belong to a given project.
projectId | the id of the project for which to retrieve all issue ids |
---|
GenericEntityException |
---|
Retrieves the Issue
that has the given key, or null if no such Issue exists.
This method will always return a new instance of an issue object if the issue exists.
key | The Issue key. |
---|
MutableIssue
with the given key, or null if no such Issue exists.DataAccessException |
---|
Retrieves an issue by id. This method will always return a new instance of an issue.
id | the id |
---|
DataAccessException |
---|
Retrieves an issue given a workflow ID. This is used when transitioning through the various steps of a workflow.
workflowId | workflow ID. |
---|
GenericEntityException |
---|
Get issues with the following ids. The issues are sorted in the order that the ids were given in. Any ids that are not found will be missing from the list. That is list will not contains nulls.
ids | Issue IDs. |
---|
MutableIssue
s
Get a list of issues related to an entity (version, component etc).
relationName | A IssueRelationConstants string indicating some relation of entity |
---|---|
entity | The entity related to the issues we're after |
MutableIssue
s associated with an entity.GenericEntityException |
---|
Get issues with the following ids. The issues are sorted in the order that the ids were given in.
ids | Issue IDs. |
---|
Get a list of issues related to an entity (version, component etc).
relationName | A IssueRelationConstants string indicating some relation of entity |
---|---|
entity | The entity related to the issues we're after |
GenericEntityException |
---|
Check existence of issues for the given set of keys
issueKeys | Set of issue keys |
---|
Returns a set of project ID / issue type combinations that given issue IDs cover.
issueIds | Set of issue IDs |
---|
Returns a set of project ID / issue type combinations that given issue keys cover.
issueKeys | Set of issue keys |
---|
Get all the issues for a given project.
project | the Project |
---|
GenericEntityException |
---|
Returns the number of unassigned issues.
Get a list of issues that the user has voted on and can see.
user | The user. |
---|
Issue
objects the user has voted on.Get a list of issues that the user has voted on.
user | The user. |
---|
Issue
objects the user has voted on.Get a list of issues that the user is watching and can see.
user | the User. |
---|
Issue
objectsGet a list of issues that the user is watching
user | the User. |
---|
Issue
objectsReturn a list of watchers for a particular issue.
issue | the Issue |
---|
Return a list of watchers for a particular issue.
issue | the Issue |
---|
Returns a boolean indicating whether there are unassigned issues.
Returns true
if the issue can be edited by the current user. This is determined by looking at both the
user's permissions and the workflow step the issue is in.
issue | the issue you want to edit |
---|---|
user | the user who will be performing the edit |
true
if the user has permission and the issue is in an editable workflow step
Returns true
if the issue can be edited. This is determined by looking at the workflow step the issue is in.
issue | the Issue. |
---|
true
if the issue can be edited. This is determined by looking at the workflow step the issue is in.
Returns true if issue with a given key exists (it looks for issues having current issue key set for the value, and moved issue keys that used the key).
GenericEntityException |
---|
Used internally when we want to record that an Issue has changed its Issue key (because it has moved project).
oldIssue | The issue with it's old issue key |
---|
This method will store the provided issue to the JIRA datastore. The issue will be saved and re-indexed. This method performs no permission checks.
This method should be used if you want to exert more control over what happens when JIRA updates an issue.
user | who is performing the operation |
---|---|
issue | the issue to update |
updateIssueRequest | details about how to perform the update, including user context, event dispatch strategy and history metadata |
This method will store the provided issue to the JIRA datastore.
The issue will be saved and re-indexed unless DO_NOT_DISPATCH
is specified.
This method performs no permission checks.
This method should be used if you want to exert more control over what happens when JIRA updates an issue. This
method will allow you to specify if an event is dispatched and if so which event is dispatched, see
EventDispatchOption
. This method also allows you to specify if email
notifications should be send to notify users of the update.
user | who is performing the operation |
---|---|
issue | the issue to update |
eventDispatchOption | specifies if an event should be sent and if so which should be sent. |
sendMail | if true mail notifications will be sent, otherwise mail notifications will be suppressed. |
Creates a MutableIssue object from an Issue GenericValue.
If a null GenericValue is passed, then null is returned.
issueGV | the Issue GenericValue. |
---|