Date: Fri, 29 Mar 2024 01:17:06 +0000 (UTC) Message-ID: <1912413989.12379.1711675026906@vps-44033663.vps.ovh.ca> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12378_1328918842.1711675026905" ------=_Part_12378_1328918842.1711675026905 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
In some cases, you can prefer to s= hare a same Workflow with different Projects, and incorporate a small delta= based on the current project.
This condition allows= the transition if the current project matches with the selected project.= p>
It is not the best practice in JIRA Administration, but it can minimize = effort during the implementation of a new configuration.
Select the Project Condition ...
Specify the expected Project,
Ok it is defined ... Now the trans= ition is allowed only if current Issue is in the Project Tes= t
The Condition configuration may be done in XML in Workflow descriptor as= follow :
<cond= ition type=3D"class"> =09<arg name=3D"class.name">fr.alkaes.myaawf.workflow.condition.Proje= ctCondition</arg> =09<arg name=3D"requiredProjectId">10100</arg> </condition>
Here the condition is valid, if th= e Required Project Id matches with current project ...
Useful hint
See also ...