The current issue that is changed by the workflow rule is referenced as
When you reference an issue in a workflow rule, you can omit the
issue and enter the property or method.
issue.Assignee = issue.reporter and
Assignee = reporter do the same.
Any property that returns a
sequence type has a set of extended properties that are available for all sequence types.
There are also operations that you can use to find, add, remove, and clear elements in the sequence.
For more information, see Sequences
The following properties are available for issues.
Each property is presented in the following format:
[property name]: [data type].
|The user who reported the issue. For example, ||Read-only|
|The date when the issue was created.||Read-only|
|The date when the issue was last updated.||Read-only|
|The date when an issue was set to a value that is considered resolved.
When an issue enters a resolved state, the ||Read-only|
|The user group for which the issue is visible. If the property contains a null value, the issue is visible to the All Users group.||Read-only|
|A list of comments that have been added to the issue. For comment-related methods, see getEditedComments and addComment.||Read-only|
|The read-only list of attachments for the issue. See also clearAttachments.||Read-only|
|The number of issues that are linked to the current issue with the ||Read-only|
|The project to which the issue is assigned. See also Project-related Methods.||Read/write|
|The text that is entered as the issue summary.||Read/write|
|The text that is entered as the issue description.||Read/write|
|The number of votes for an issue. For vote-related methods, see canVoteIssue, voteIssue, canUnvoteIssue, and unvoteIssue.||Read/write|
|The list of tags that are attached to an issue. For tag-related methods, see hasTag, addTag, removeTag, getTag, and getSharedTag.||Read/write|
|The issue number in the project.||Read/write|
|The list of issues that are linked to the current issue with the specified link type name.||Read/write|
|The value for the specified custom field. For example, ||Read/write|
|The list of sprints to which an issue is assigned.||Read/write|
The following properties are available for comments.
The following properties are available for attachments.
The following properties are available for tags.
|The name of the tag.||Read-only|
|The user who is the owner of the tag.||Read-only|
Changes that are applied to issue are managed by a series of transactions. A transaction is a collection of current changes that are either saved to the database or discarded as a set. When a user edits an issue, a new transaction is started. The transaction is completed when the user clicks the Submit button. The single transaction includes all of the changes that were made to the issue.
Rules that are not executed according to a schedule are processed at the end of a transaction. Scheduled rules and scheduled blocks in state-machine rules are only processed for issues that are already reported or become reported in the current transaction.
The following methods are available for use with issues.
The syntax for each method is presented in the following format:
[method](parameter: [data type]): [data type].
|Description||Returns the issue ID.|
|Description||Returns the issue URL.|
|Description||Clones the current issue.|
|Description||Remove all of the attachments from an issue.|
|Parameters||The name of the tag to check for an the issue.|
|Description||Checks whether the specified tag is attached to an issue.|
|Description||Checks whether any user has added the star tag to an issue.|
Issue Lifecycle Methods
The following methods are related to the lifecycle of an issue. The lifecycle of an issue consists of the following stages:
The following methods are related to the
This property is set based on the values that are stored in a custom field with a
state data type.
Each value that can be stored in this field has a Resolved property.
This property determines whether the issue is considered to be resolved when it assigned a value for this field.
resolved property is associated with the issue, which means that these methods do not contain references to the custom field.
|Description||Checks whether an issue is assigned a state that is considered resolved.|
These methods can be used to send notifications to unregistered users with an email address. To send notifications to existing users, use the following methods:
|Sends an email notification to the email address that is set in the user profile.|
|Sends a notification message over Jabber.|
|Sends an email notification to all of the users who are members of the group.|