Details
-
Bug
-
Resolution: Fixed
-
High
-
3.7.1, 3.7.2, 3.7.3, 3.7.4, 3.8, 3.8.1, 3.9, 3.9.1, 3.9.2, 3.9.3, 3.10, 3.10.1, 3.10.2, 3.11, 3.12
-
3.07
-
Description
If we have a Jelly script, running a filter that results >1 issue, and transitioning them, eg:
<JiraJelly xmlns:jira="jelly:com.atlassian.jira.jelly.enterprise.JiraTagLib" xmlns:core="jelly:core" xmlns:log="jelly:log"> <jira:RunSearchRequest filterid="10020" var="issues" /> <core:forEach var="issue" items="${issues}"> <log:warn>Transitioning issue ${issue.key}</log:warn> <jira:TransitionWorkflow key="${issue.key}" workflowAction="Resolve Issue"/> </core:forEach> </JiraJelly>
Then all transitioned issues will have their assignee set to that of the first encountered issue.
Attachments
Issue Links
- relates to
-
JRASERVER-11768 Jelly TransitionWorkflow tag forces issue to be reassigned
- Closed