-
Suggestion
-
Resolution: Low Engagement
-
None
Problem Definition
When there is a workflow that is using an invalid status, the Board's configuration will turn out blank. This is a bug reported in https://jira.atlassian.com/browse/JSWSERVER-13881
In order to identify the responsible workflow so that the invalid status can be removed is a difficult process and is not practical. There is a need for a better way.
Suggested Solution
- Include the responsible/affected workflow in the log stack trace when opening the Board's configuration
- Provide a REST API or a way to run an Integrity check for a workflow with an invalid issue status
Workaround
As of now, the KB: https://confluence.atlassian.com/display/JIRAKB/Internal+Server+Error+when+accessing+Rapid+board
- is related to
-
JSWSERVER-13881 Board Configuration returns a blank screen if JIRA has a workflow with a missing status
-
- Closed
-
[JSWSERVER-20124] As Jira Administrator I want a way to identify workflows that has an invalid status
Resolution | New: Low Engagement [ 10300 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Labels | Original: pse-request supportability | New: cleanup-seos-fy25 pse-request supportability |
Workflow | Original: JAC Suggestion Workflow [ 3270470 ] | New: JAC Suggestion Workflow 3 [ 3663543 ] |
Affects Version/s | New: 7.6.12 [ 85502 ] |
Affects Version/s | New: 7.13.4 [ 86493 ] |
Labels | New: pse-request supportability |
Link |
New:
This issue is related to |