-
Bug
-
Resolution: Won't Fix
-
Low (View bug fix roadmap)
-
None
-
6.1
-
6.01
-
JIRA appears to not validate workflow XML when importing it. This means that you could import a workflow which refers to statuses which do not exist in the system.
If a project which uses such a workflow is shown on a board, then when a user attempts to configure the board, they will see an Internal Server Error with the following stack trace:
2013-01-13 17:57:05,450 http-bio-9080-exec-2521 ERROR mtokar 1077x545487x3 1mggf6n 59.167.133.100,172.16.3.10 /rest/greenhopper/1.0/rapidviewconfig/editmodel.json [common.error.jer
sey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
java.lang.NullPointerException
at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.asStatusEntry(ColumnEditHelper.java:295)
at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnStatusesModel(ColumnEditHelper.java:283)
at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnEditModel(ColumnEditHelper.java:178)
at com.atlassian.greenhopper.web.rapid.view.RapidViewEditHelper.getEditModel(RapidViewEditHelper.java:125)
at com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$6.call(RapidViewEditResource.java:182)
at com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$6.call(RapidViewEditResource.java:175)
Although JIRA should fix this so that validation occurs, we can also add a null check to ensure that such problematic workflows do not break GreenHopper. This should not be a common occurrence.
- is caused by
-
-
- Gathering Impact
-
-
JRASERVER-43561 Validate workflow integrity before allowing addition to workflow scheme
- Gathering Interest
- relates to
-
- Closed
- derives
-
JRADEV-18110 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Internal Server Error when accessing board configuration if workflow steps and statuses are not configured correctly
-
-
Resolution: Won't Fix
-
Low (View bug fix roadmap)
-
None
-
6.1
-
6.01
-
JIRA appears to not validate workflow XML when importing it. This means that you could import a workflow which refers to statuses which do not exist in the system.
If a project which uses such a workflow is shown on a board, then when a user attempts to configure the board, they will see an Internal Server Error with the following stack trace:
2013-01-13 17:57:05,450 http-bio-9080-exec-2521 ERROR mtokar 1077x545487x3 1mggf6n 59.167.133.100,172.16.3.10 /rest/greenhopper/1.0/rapidviewconfig/editmodel.json [common.error.jer
sey.ThrowableExceptionMapper] Uncaught exception thrown by REST service
java.lang.NullPointerException
at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.asStatusEntry(ColumnEditHelper.java:295)
at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnStatusesModel(ColumnEditHelper.java:283)
at com.atlassian.greenhopper.web.rapid.view.ColumnEditHelper.buildColumnEditModel(ColumnEditHelper.java:178)
at com.atlassian.greenhopper.web.rapid.view.RapidViewEditHelper.getEditModel(RapidViewEditHelper.java:125)
at com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$6.call(RapidViewEditResource.java:182)
at com.atlassian.greenhopper.web.rapid.view.RapidViewEditResource$6.call(RapidViewEditResource.java:175)
Although JIRA should fix this so that validation occurs, we can also add a null check to ensure that such problematic workflows do not break GreenHopper. This should not be a common occurrence.
- is caused by
-
-
- Gathering Impact
-
-
- Gathering Interest
- relates to
-
- Closed
- derives
-
JRADEV-18110 Loading...
-
Unassigned
-
Michael Tokar
- Votes:
-
0 Vote for this issue
- Watchers:
-
4 Start watching this issue
- Created:
- Updated:
- Resolved: