| 2188 |
jgill |
1 |
#MoveIssue_en.properties
|
|
|
2 |
moveissue.assignable.user=This user does not have the ''Assignable User'' permission in the target project
|
|
|
3 |
moveissue.assignee.invalid=The assignee is not valid within the target project.
|
|
|
4 |
moveissue.components.field.required=The "{0}" field is required and the target project "{1}" does not have any components.
|
|
|
5 |
moveissue.confirm=Confirm
|
|
|
6 |
moveissue.confirm.field.hidden=HIDDEN
|
|
|
7 |
moveissue.create.attachment.permission=You do not have the "Create Attachment" permission in the target project and this issue has attachments.
|
|
|
8 |
moveissue.currentissue=Current Issue
|
|
|
9 |
moveissue.currentissuetype=Current Issue Type
|
|
|
10 |
moveissue.currentproject=Current Project
|
|
|
11 |
moveissue.currentstatus=Current Status
|
|
|
12 |
moveissue.customfield.notapplicable=This custom field is not applicable.
|
|
|
13 |
moveissue.customfield.notapplicable.lost=This custom field is not applicable - this data will be lost.
|
|
|
14 |
moveissue.description.required=The "Description" field is required in the target field layout scheme.
|
|
|
15 |
moveissue.duedate.required=The "Due Date" field is required in the target field layout scheme.
|
|
|
16 |
moveissue.duedate.schedule.permission=The "Due Date" is required in the target field layout scheme but you do not have permission to "Schedule Issues".
|
|
|
17 |
moveissue.environment.required=The "Environment" field is required in the target field layout scheme.
|
|
|
18 |
moveissue.error=An error has occurred while attempting to move the issue.
|
|
|
19 |
moveissue.error.assignee.required=The "{0}" field is required and you do not have any valid assignees for the target project "{1}".
|
|
|
20 |
moveissue.error.attachment=An error occurred accessing the attachments for this issue.
|
|
|
21 |
moveissue.error.due.date=Error setting due date on issue.
|
|
|
22 |
moveissue.error.duedate.required=The "{0}" field is required and you do not have permission to "Schedule Issues" in the target project "{1}".
|
|
|
23 |
moveissue.error.field.layout.access=Error accessing field layout scheme.
|
|
|
24 |
moveissue.error.fixfors.required=The "{0}" field is required and you do not have permission to Resolve Issues in the target project "{1}".
|
|
|
25 |
moveissue.error.versions.required=The "{0}" field is required and the target project "{1}" does not have any versions.
|
|
|
26 |
moveissue.field.hidden=This field is hidden in the target field layout scheme.
|
|
|
27 |
moveissue.newissuetype=New Issue Type
|
|
|
28 |
moveissue.newproject=New Project
|
|
|
29 |
moveissue.newstatus=New Status
|
|
|
30 |
moveissue.newvalue=New Value (after move)
|
|
|
31 |
moveissue.no.assign.permission=You do not have the "Assign Issue" permission and the current assignee is not assignable in the target project.
|
|
|
32 |
moveissue.no.create.permission=You do not have the "Create Issue" permission in the target project.
|
|
|
33 |
moveissue.no.permission=You do not have permissions to perform this operation.
|
|
|
34 |
moveissue.notapplicable=N/A
|
|
|
35 |
moveissue.originalvalue=Original Value (before move)
|
|
|
36 |
moveissue.remain.assigned=The issue will remain assigned to {0}.
|
|
|
37 |
moveissue.remain.unassigned=The issue was unassigned and will remain unassigned in the new project.
|
|
|
38 |
moveissue.removeprojectcf=This custom field value will be removed, as it is defined with project scope.
|
|
|
39 |
moveissue.select.status=Select Status
|
|
|
40 |
moveissue.select.user=Please select a valid user
|
|
|
41 |
moveissue.selectissuetype=Select Issue Type
|
|
|
42 |
moveissue.selectproject=Select Project
|
|
|
43 |
moveissue.set.assignee.error=An error occurred setting the assignee for this issue.
|
|
|
44 |
moveissue.status.invalid=Each status displayed below is invalid - please select a new status
|
|
|
45 |
moveissue.step1.desc.ent=<b>Step 1 of 4</b>\: Choose the project and issue type to move to ...
|
|
|
46 |
moveissue.step1.desc.pro=<b>Step 1 of 3</b>\: Choose the project to move to ...
|
|
|
47 |
moveissue.step2.desc.ent.both=<b>Step 2 of 4</b>\: Select the status of the issue and the subtask(s) ...
|
|
|
48 |
moveissue.step2.desc.ent.error=<b>Note</b>\: You must select a target workflow.
|
|
|
49 |
moveissue.step2.desc.ent.issueonly=<b>Step 2 of 4</b>\: Select the status of the issue ...
|
|
|
50 |
moveissue.step2.desc.ent.subtaskonly=<b>Step 2 of 4</b>\: Select the status of the subtask(s) ...
|
|
|
51 |
moveissue.step2.desc.pro=<b>Step 2 of 3</b>\: Update the fields of the issue to relate to the new project.
|
|
|
52 |
moveissue.step2.notrequired=Step 2 is not required
|
|
|
53 |
moveissue.step3.desc.ent=<b>Step 3 of 4</b>\: Update the fields of the issue to relate to the new project.
|
|
|
54 |
moveissue.step3.desc.pro=<b>Step 3 of 3</b>\: Confirm the move with all of the details you have just configured.
|
|
|
55 |
moveissue.step4.desc.ent=<b>Step 4 of 4</b>\: Confirm the move with all of the details you have just configured.
|
|
|
56 |
moveissue.subtask.cannot.move=Sub-tasks cannot be moved independently of the parent issue.
|
|
|
57 |
moveissue.subtasks=Sub-Tasks
|
|
|
58 |
moveissue.taskswithstatus=tasks with status
|
|
|
59 |
moveissue.taskwithstatus=task with status
|
|
|
60 |
moveissue.title=Move Issue
|
|
|
61 |
moveissue.update.fields=Update Fields
|
|
|
62 |
moveissue.workflow=Workflow
|