Date: Tue, 19 Mar 2024 07:39:59 +0000 (UTC) Message-ID: <726076567.12071.1710833999652@vps-44033663.vps.ovh.ca> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_12070_1940297455.1710833999651" ------=_Part_12070_1940297455.1710833999651 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The Auto-Transitions Manager is responsible of
Its behavior may be altered by Auto-Transition Properties.
For a specified Issue, the Auto-= Transitions Manager will process as follow :
<acti= on id=3D"100" name=3D"Close" view=3D"resolveissue"> =09... =09<meta name=3D"allow.auto.transition">true</meta> =09... </action>
Depending on the transition defintion, a Screen may be associated. That = means that values will have to be filled during the transition.
Since there is no human interaction, you will have to define the values = to use on the transition.
To do that the Auto-Transitions Manager read all Transi= tion Properties prefixed with auto.transition., and assume= s the end of the property as the field Id.
By example, if the Transition Screen has the resolution field, the wante= d value (Resolution Id.) has to be defined using Transition Property auto.t= ransition.resolution ...
<acti= on id=3D"100" name=3D"Close" view=3D"resolveissue"> =09... =09<meta name=3D"auto.transition.resolution">1</meta> =09... </action>
<acti= on id=3D"100" name=3D"Close" view=3D"resolveissue"> =09... =09<meta name=3D"auto.transition.customfield_10010">admin</meta>= ; =09... </action>
Each defined field's values are injected in the context in order to perf= orm the transition.
When the Transition is performed, a comment is added to the Issue. But i= t is possible to modify this behavior using Transition Properties.
See Properties overview below
Properties | Values | Description |
---|---|---|
allow.auto.transition | True or False | True if the Transition may be assumed as a Auto-= Transition |
auto.transition.fieldId | Any valid value | Associated value is used in Transition Context f=
or field identified by the Id. fieldId If the field may have already a value before the transition, no change wil= l be done if the special value --unchanged-- is specified.= |
auto.transition.unchangeMissingFields | If presents, any missing field of the transition= screen will be let unchanged with previous value | |
comment.auto.transition.enabled | True or False | True (default) if want a comment added for each = performed Transition. |
comment.auto.transition | Text to use as comment ... | This text support String substitution whrere {0}= is the action Id. and {1} is the issue key. |
This sample transition:
<actio= n id=3D"100" name=3D"Close" view=3D"resolveissue"> =09<meta name=3D"jira.description">Close Transition reserved to AutoT= ransitionService</meta> =09<meta name=3D"jira.i18n.title">WFA_Close</meta> =09<meta name=3D"allow.auto.transition">true</meta> =09<meta name=3D"auto.transition.resolution">1</meta> =09<meta name=3D"auto.transition.assignee">--unchanged--</meta> =09<meta name=3D"auto.transition.unchangeMissingFields"></meta> =09<restrict-to> =09=09<conditions type=3D"AND"> =09=09=09<condition type=3D"class"> =09=09=09=09<arg name=3D"class.name">com.atlassian.jira.workflow.cond= ition.InactivityCondition</arg> =09=09=09=09<arg name=3D"onWorklog">15d</arg> =09=09=09</condition> =09=09=09<condition type=3D"class"> =09=09=09=09<arg name=3D"class.name">com.atlassian.jira.workflow.cond= ition.ExtendedPermissionCondition</arg> =09=09=09=09<arg name=3D"permission">admin</arg> =09=09=09</condition> =09=09</conditions> =09</restrict-to> =09<post-functions> =09=09<function type=3D"class"> =09=09=09<arg name=3D"class.name">com.atlassian.jira.workflow.functio= n.issue.UpdateIssueStatusFunction</arg> =09=09</function> =09=09<function type=3D"class"> =09=09=09<arg name=3D"class.name">com.atlassian.jira.workflow.functio= n.misc.CreateCommentFunction</arg> =09=09</function> =09=09<function type=3D"class"> =09=09=09<arg name=3D"class.name">com.atlassian.jira.workflow.functio= n.issue.GenerateChangeHistoryFunction</arg> =09=09</function> =09=09<function type=3D"class"> =09=09=09<arg name=3D"class.name">com.atlassian.jira.workflow.functio= n.issue.IssueReindexFunction</arg> =09=09</function> =09=09<function type=3D"class"> =09=09=09<arg name=3D"eventTypeId">5</arg> =09=09=09<arg name=3D"class.name">com.atlassian.jira.workflow.functio= n.event.FireIssueEventFunction</arg> =09=09</function> =09</post-functions> </action>
Useful hint
See also ...