Details
-
Bug
-
Resolution: Timed out
-
Low
-
None
-
4.2.1
-
4.02
-
Severity 3 - Minor
-
-
Description
See this issue: https://studio.atlassian.com/browse/JST-3918
In this case, the customer was using the default screen for the transition, which included the ability to update the issue type. We were progressing this transition in response to a commit message from SVN, and were updating none of the fields, however, JIRA seems to be ignoring the fact that no issue type was set on the transition request, and updates the issue type of the issue to be null. This later results in a NullPointerException when permissions are checked for another field.
This may be a problem for other fields, not sure. It seems here that the assumption is that because issue type is a select list, that it will always have a value. That's true when the transition is executed from the web interface, but its not true in any other workflow transition scenario. It also seems that the issue type field might not be being correctly validated before being set. What should happen is that it should be seen to be null in the transition request, and so not updated.