Date: Fri, 29 Mar 2024 09:38:50 +0000 (UTC) Message-ID: <1595346942.33.1711705130956@7e89cb4762e5> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_32_2082912020.1711705130955" ------=_Part_32_2082912020.1711705130955 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
You can copy the value of a source field to a destination field.=
Click the +
button to add additional field pairs to your=
configuration.
Keep in mind that not all conv= ersions from source to destination field are supported, nor feasible. We ca= n only ensure that it will work if the source and destination fields are of= the same field type, or the destination field is a text field. Some additi= onal combinations of different field types might work although not <= em>officially supported.
For text fields and other fields that can accept multiple values (like c= heckboxes), you can choose to overwrite, append, or prepend the new value t= o any existing value. For a text field, you can also choose a separator tha= t is placed between the values (not shown in the screenshot above).
Imagine your origin issue has a version that you want to copy to the lin= ked issue. If the destination field is 'Fix Version/s', 'Affects Version/s'= or some custom field of type 'Version Picker', you can define that a new v= ersion will be created in the target project, if it does not yet exist. If = you don't choose this option and that version does not yet exist, the user = receives an error message and the transition completes.
A user needs the Administer Pr= ojects permission to be able to create a new version.
Imagine your origin issue has a component that you want to copy to the l= inked issue. If the destination field is Components, you define th= at a new component is created in the target project, if it does not yet exi= st. If you don't choose this option and that component does not yet exist, = the user receives an error message and the transition completes.
A user needs the Administer Projects permission to create a new componen= t.
*** empty ***
: The destination field will be cleared.=
*** last comment ***
: The last commen=
t from the source issue will be copied. In some cases that might be the com=
ment from the transition screen, which the user just entered while performi=
ng the current transition.
*** new comment ***
: A new comment will be created wi=
th the copied value. When you choose to overwrite to new comment, a new com=
ment is created, enabling you to add multiple comments in one post function=
.
Examples:Copy Description to New Comment, o=
verwrite
=E2=86=92 creates a new comment with =
the description.Copy Summary to New Comment, append with separato=
r ", "
=E2=86=92 appends the summary to the pr=
eviously created comment, so the comment will look like <Description>=
, <Summary>.Copy Assignee to New Comment, overwrite
&=
nbsp;=E2=86=92 creates a new comment.
This configuration will result in two comments being created; one with the =
description and summary, and one with the assignee.