| Table of Contents |
|---|
| maxLevel | 2 |
|---|
| minLevel | 2 |
|---|
| type | flat |
|---|
| separator | pipe |
|---|
|
...
| Column |
|---|
|
 Image Removed |
...
...
To install, go to UPM, find the Upload Add-on dialog, and paste in the snapshot link into the url field.
2013-
...
12-
...
17
Highlights
| Section |
|---|
| Column |
|---|
| Tip |
|---|
| title | Recommendation for JSPs |
|---|
| - Current users should update their JSPs from using the 23.50.0 distribution zip or later. This is necessary for JCPP-64.
|
|
|
| Section |
|---|
| Column |
|---|
|
|
| Column |
|---|
More Major new customization capabilitiesimprovements- Clone option check box defaults can now be configured in the clone properties file. Similar to other customizations, the defaults can be configured separately for each custom operation.
- Fix versions and affected versions are now available as substitution variables in clone properties.
|
|
| Section |
|---|
| Column |
|---|
| Image Removed |
| Column |
|---|
ImprovementsOther improvements and fixes. |
|
- Due date and environment can now be set via properties.
- More unique customization operations can now be configured via properties - up to 16 unique clone operations
- Substitution variables have been extensively expanded and made consistent
- Existing variables in original format preserved for upward compatibility - recommend updating to new format to ease future maintenance as new variables are added
- New format consistent with Create on Transition for Jira and CW
- Values can now be drawn from original issue (that initiated the clone), current issue or subtask being cloned, and the parent of the new clone
- Documentation improvements - see Customization - Archived User Comments
| Info |
|---|
| title | Programming based customization |
|---|
| With version 3.0, must customization scenarios have been covered using the clone properties file approach. Because of this, we are deprecating and discontinuing active support for programming based customization. Documentation has been removed, although current programs should continue to work as before. User are encouraged to convert to property based approach as much as possible and Open issues for additional support if necessary. |
|
|
| Section |
|---|
| Column |
|---|
| Image Modified |
| Column |
|---|
Resolved Issues| Jira Legacy |
|---|
| server | System JIRA (bobswift.atlassian.net) |
|---|
| columns | type,key,summary,reporter,assignee,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = JCPP AND fixVersion = "23.50.0" ORDER BY priority DESC |
|---|
| serverId | 729d679a8382ec9d-302cabb6-339f3a29-958b8d72-015e107badcd95b9a5732a63 |
|---|
|
|
|