Page Comparison

...

...

{csv:output=wiki}
Plugin \ JIRA,  4.0, 4.1, 4.2, 4.3, 4.4, 5.0, Tested releases 

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"
{csv}

...

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: @summary@, description: @description@, reporter: @reporter@, 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: @summary@, description: @description@, reporter: @reporter@, assignee: @assignee@, security: @security@ 1.set.subtask.issuetype = Sub-task

4. Additional pre-defined custom actions

...

...

Resolved Issues