Create a Project Activity

Fields

For any created issues, field values stored in the issue component template files may be replaced by other values, described here below

• Key: Project key cannot be kept, as all issues should bear different keys. A new key will be created. No warning will be emitted.
• Reporter: value to be replaced with the user who created the activity. No warning.
• Assignee: value to be used is stored in the file. If the user is not found, then Unassigned should be used.
• Status and Resolution: will all be ignored and replaced with the entry state of the current workflow
• Priorities: if not found, will be set to a default value.
• Labels will be kept if existing, otherwise they will be ignored.
• fixVersion and affectVersions: will be kept, if existing in the current project. Otherwise, they will be ignored.
• Issue LInks : will be kept if and only if both issues linked together are in the issue component template file and if issue link type exist. Otherwise, it will be ignored.
• Estimate and Original Times : will be kept as is.
• All Dates: except for Due Date, will all be ignored and restored. Logged times will be ignored. No warning will be emitted.
• Comments : will all be deleted, no warnings.
• HTML formatting in descriptions: will be lost. Please use wiki markups. No warnings.

All above unless stated otherwise will generate a warning when a field value cannot be used as is. Please report bugs if you don't see this.

Issue Type Supports

• Epics will be supported. But any ranking or colors stored previously will be restored.
• Sprints are not created.

In a future release, it will be possible to automatically fill the following field of each Issue created by a value selected at creation time:

• fixVersion
• Affected Version
• Component
• Assignee
• Reporter
• Sprint