java.lang.Object | |
↳ | com.atlassian.jira.web.bean.BulkEditBeanImpl |
Implementation of BulkEditBean.
BulkEditBean was originally a concrete class, but it has been made abstract in order to separate API and implementation in JIRA.
[Expand]
Inherited Constants | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From interface
com.atlassian.jira.web.bean.BulkEditBean
|
Public Constructors | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
[Expand]
Inherited Methods | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
From class
java.lang.Object
| |||||||||||
From interface
com.atlassian.jira.issue.customfields.OperationContext
| |||||||||||
From interface
com.atlassian.jira.web.bean.BulkEditBean
| |||||||||||
From interface
com.atlassian.jira.web.bean.SingleIssueModeEditBean
|
This method is deprecated.
No replacement.
Use for testing ONLY
Returns all the unique field layouts of the selected issues
This method is used to get a target issue that will provide the correct context (i.e. project and issue type), for where you are moving to. The object returned is not mapped to a specific selected issue.
Gets issues whose status is null
Issue
objects. Emoty Set if no invalid issuesWorkflowException |
---|
Gets a set of invalid statuses that are not valid in the destination workflow
WorkflowException |
---|
Returns a string that represents a "unique" identifier for this bulke edit bean
If there is a limit on the number of issues that can be bulk edited, this will return that number, otherwise -1.
returns a list of project ids for projects which the currently selected issues belong to.
Returns a list of "selected" issues. For the "top level" BulkEditBean this should be the actual issues chosen by the user for the bulk operation.
The Bulk Move operation will then break this list up in groups of project and issue type and store each of these types in its own BulkEditBean, so for these nested BulkEditBeans this list may be a subset of the original selected issues. Furthermore when moving parent issues to a new Project, we will have to move any subtasks as well. In this case a third level of BulkEditBean is created and these ones will have subtasks that may not have been explicitly selected by the user at all.
Gets the issue key for this bean as previously set
by setSingleIssueKey(String)
.
null
if there is none.
Returns the single Project if there is only one Project in this BulkEditBean, otherwise throws an IllegalStateException.
This is a convinience method for converting the list of objects to a list of GenericValues
Get the transition errors after bulk issue transition
Initialises the BulkEditBean
with the selected issues
selectedIssues | Required selected Issues. |
---|
Check if a mail server has been specified.
Indicates where this bean is being used to move a single issue with subtasks.
true
if this bulk edit bean is used for single issue move operation
Sets the maximum number of issues allowed to be bulk edited at once. Use -1 to indicate no limit.
maxIssues | either -1 or a positive integer representing the maximum number of issues allowed for bulk edit. |
---|
If this BulkEditBean contains subtasks of another BulkEditBean, then we can set a pointer back to the BulkEditBean containing the parent issues. This is used so that the subtask issues have access to the new values in their parent issues. See JRA-13937 where we had to ensure that the subtasks in a Bulk Move could get to the new Security Level of their parents.
parentBulkEditBean | The BulkEditBean that contains parent issues of the issues (subtasks) in this BulkEditBean. |
---|
Sets this bean to "single issue mode". Set single issue key to be moved via bulk edit workflow.
singleIssueKey | key for single issue to be moved |
---|
Sets the targetFieldLayout to the appropriate FieldLayout (aka "Field Configuration") for the target Project and Issue Type.