-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Medium
-
Component/s: Queues - Bulk Actions
-
7
-
Severity 3 - Minor
-
19
Issue Summary
If you have a workflow transition where you can "move" issues from "Any Status" to "Itself", you cannot use this transition from the Project Queue view (bulk transition) for any issue.
The use case for this setup:
While having different queues within the same project, users might need to move the tickets between the queues, and change/add values for different fields and components. With that, having a transition from any status to itself and adding a transition screen for that helps to address this requirement.
Steps to Reproduce
- Edit the workflow for a given Issue/Request Type and add a transition from "Any Status" to "Itself":


- Access the JSM Project > Queues > Select an issue > hit the "Transition" Button > Select the self-transition we previously configured:

Expected Results
The ticket should be transitioned to the same status
Actual Results
The below exception is thrown in the logs:
stack: java.lang.NullPointerException: stepDescriptor
at java.util.Objects.requireNonNull(Unknown Source)
at com.atlassian.jira.workflow.JiraWorkflowUtils.getLinkedStatusId(JiraWorkflowUtils.java:31)
ext: { [-]
err: { [-]
location: com.atlassian.jira.workflow.JiraWorkflowUtils:getLinkedStatusId
type: java.lang.NullPointerException
}
jira: { [-]
request: { [-]
id: c768300d141ed8bb87a9b77a0af5d16a
ipaddr: 54.81.76.127
method: POST
normuri: BulkTransitionIssue
traceId: 2b063e9200718535
traceSampled: false
url: /secure/BulkTransitionIssue.jspa
message: Failed to serialize JSON for bulk transition.
micros_container: jira
From the UI:
The tickets couldn’t be transitioned Try again soon or get in touch with our support team.

An unknown error occurred. If it persists, please contact support

Workaround
The suggested workaround is to open the ticket on a new tab and execute the transaction directly through the issue view.
- mentioned in
-
Page Loading...