Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

maxLevel2

...

minLevel2
typeflat
separatorpipe

Section


Column

22 February 2012

Summary

This release provides major improvements and fixes especially related to customization support. Also UI improvements.

Tip
titleJSPs need to be updated

Level 1.3.0 of the JSPs should be installed with this release.

Compatibility

Csv
outputwiki

Plugin \ JIRA,  4.0, 4.1, 4.2, 4.3, 4.4, 5.0, Tested releases [!GINT:Home^gint-tested-small.png!|GINT:] 
1.3.1v5,        (x), (x), (x), (x), (x), (/), "5.0.0"
1.3.1,          (x), (x), (x), (/), (/), (x), "4.3.3, 4.4.3"
1.3.0v5,        (x), (x), (x), (x), (x), (/), "5.0-rc1, 5.0.0"
1.3.0,          (x), (x), (x), (/), (/), (x), "4.3.3, 4.4.3"
1.2.0,          (x), (!), (/), (/), (/), (x), "4.2.4, 4.3.3, 4.4.3"
1.1.2,          (x), (!), (/), (/), (/), (x), "4.2.4, 4.3.3, 4.4.1"
1.1.1,          (x), (!), (/), (/), (/), (x), "4.2.4, 4.3.3, 4.4.1"
1.1.0,          (x), (!), (/), (/), (!), (x), "4.2.4, 4.3.3, 4.4.0"



Column
width30%


Info
titleDownloads

Release notes

Include Page
JCPP:Release notesNotesJCPP:
Release notesNotes


Highlights of

...

Clone Plus

...

for JIRA 1.3.0

Section


Column
width60px


Column

Customization improvements


  1. 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
    


  2. 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
    


  3. 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
    


  4. Additional pre-defined custom actionsoperations
Tip
titleCustomization documentation

More information will be available soon. Code improvements are also in progress - please add improvement issues and/or comments if you have specific requirements.

  • Customization documentation is still in progress - watch this page:
How to customize


Section


Column
width60px


Column

JIRA 5.x support



Section


Column
width60px


Column

UI improvements

  1. Multi-tab support
  2. Clone options


...

Resolved Issues

...

Jira Legacy
serverSystem JIRA
columnstype,key,summary,reporter,assignee,priority,status

...

maximumIssues20
jqlQueryproject

...

= JCPP

...

AND

...

fixVersion = "1.3.0" ORDER BY priority DESC
serverId8382ec9d-abb6-3a29-8d72-95b9a5732a63