-
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 | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-7127] Internal Server Error when accessing board configuration if workflow steps and statuses are not configured correctly
Many thanks for reporting this issue. Realistically, we are not planning on addressing it in the next 12 months.
Regards,
JIRA Software Team
Could you please take care issue below?
-process import new workflow jira should generate new status is in new workflow.
That is something for JIRA to solve, as GreenHopper does not handle the importing of workflows. There is an open issue in JIRA's project for this - JRA-9960.
I fixed this problem by check statuses(http://localhost:8087/jira/secure/admin/ViewStatuses.jspa) match with workflow.
I got this problem because I import new workflow but jira not generate status in workflow
After I create status into http://localhost:8087/jira/secure/admin/ViewStatuses.jspa According to workflow.
I found problem refer status by id so workflow refer wrong status display in workflow diagram.
Could you please take care issue below?
-process import new workflow jira should generate new status is in new workflow.
krisda wattanajarupong
added a comment - - edited I fixed this problem by check statuses( http://localhost:8087/jira/secure/admin/ViewStatuses.jspa ) match with workflow.
I got this problem because I import new workflow but jira not generate status in workflow
After I create status into http://localhost:8087/jira/secure/admin/ViewStatuses.jspa According to workflow.
I found problem refer status by id so workflow refer wrong status display in workflow diagram.
Could you please take care issue below?
-process import new workflow jira should generate new status is in new workflow.
Adding a validation when associating the invalid workflow to the workflow scheme would avoid this problem. Please add your votes on https://jira.atlassian.com/browse/JRASERVER-43561