Table of Contents | ||||||||
---|---|---|---|---|---|---|---|---|
|
Section | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Highlights of JIRA Clone Plus Plugin 1.3.0
...
- Exclude fields support extended to standard fields
No Format # Exclude standard fields, be careful not to exclude required fields #- Previously only custom fields supported # You must use JIRA defined literals: # versions (for affects versions), assignee, components, summary, description, duedate, environment, fixVersions, priority, reporter, security, timetracking, labels 1.fieldExcludes = versions, fixVersions, custom2, custom three
- Allow setting standard fields including summary, description, assignee, reporter, priority (id) and security level (by name or id)
No Format 1.set.summary = property summary text 1.set.description = summary: <at:var at:name="summary" />@summary@, description: <at:var at:name="description" />@description@, reporter: <at:var at:name="reporter" />@reporter@, assignee: <at:var at:name="assignee" /> @assignee@ 1.set.reporter = admin 1.set.assignee = developer 1.set.priority = 1
- Allow setting of subtask fields when cloning subtask issues
No Format 1.set.subtask.description = summary: <at:var at:name="summary" />@summary@, description: <at:var at:name="description" />@description@, reporter: <at:var at:name="reporter" />@reporter@, assignee: <at:var at:name="assignee" />@assignee@, security: <at:var at:name="security" /> @security@ 1.set.subtask.issuetype = Sub-task
- Additional pre-defined custom actions
Tip | ||
---|---|---|
| ||
More information will be available soon. Code improvements are also in progress - please add improvement issues and/or comments if you have specific requirements.
|
...
Section | |||||||
---|---|---|---|---|---|---|---|
|
...
Jira Issues | ||||||||
---|---|---|---|---|---|---|---|---|
|