-
Bug
-
Resolution: Unresolved
-
Low (View bug fix roadmap)
-
None
-
7.5.4, 7.6.3
-
7.05
-
2
-
Severity 3 - Minor
-
Issue Summary
The Sprint field value is removed on specific transition when using jira.issue.editable = false workflow property and Issue Closed event.
Steps to Reproduce
- Create a board
- Create a sprint (but do not start it)
- Create an issue on the board and assign it to the Sprint
- Configure a workflow with the jira.issue.editable = false property on the closed status
- Configure a post-function to trigger the Issue Closed event on the close transition
- Trigger the Close transition
- The Sprint field will be removed from the issue entirely. This does not happen when you have any other event configured, or not the editable property set up
Expected Results
Sprint field value remains as is.
Actual Results
Sprint field value is removed upon transition.
Workaround
Update the workflow post-function to use 'Issue Resolved' event.
- relates to
-
-
- Gathering Impact
-
[JSWSERVER-16369] Sprint field removed on specific transition when using jira.issue.editable = false and Issue Closed event
| Support reference count | Original: 1 | New: 2 |
| Description |
Original:
h3. Issue Summary
The Sprint field value is removed on specific transition when using {{jira.issue.editable = false}} workflow property and Issue Closed event. h3. Steps to Reproduce # Create a board # Create a sprint (but do not start it) # Create an issue on the board and assign it to the Sprint # Configure a Workflow with the {{jira.issue.editable = false}} property on the closed status # Configure a postfunction to trigger the {{Issue Closed}} event on the close transition # Trigger the {{Close}} transition # The Sprint field will be removed from the issue entirely. This does not happen when you have any other event configured, or not the editable property set up h3. Expected Results Sprint field value remains as is. h3. Actual Results Sprint field value is removed upon transition. h3. Workaround Update the workflow post-function to use 'Issue Resolved' event. |
New:
h3. Issue Summary
The Sprint field value is removed on specific transition when using {{jira.issue.editable = false}} workflow property and Issue Closed event. h3. Steps to Reproduce # Create a board # Create a sprint (but do not start it) # Create an issue on the board and assign it to the Sprint # Configure a workflow with the {{jira.issue.editable = false}} property on the closed status # Configure a post-function to trigger the {{Issue Closed}} event on the close transition # Trigger the {{Close}} transition # The Sprint field will be removed from the issue entirely. This does not happen when you have any other event configured, or not the editable property set up h3. Expected Results Sprint field value remains as is. h3. Actual Results Sprint field value is removed upon transition. h3. Workaround Update the workflow post-function to use 'Issue Resolved' event. |
| Description |
Original:
h3. Issue Summary
h3. Steps to Reproduce # Create a board # Create a sprint (but do not start it) # Create an issue on the board and assign it to the Sprint # Configure a Workflow with the {{jira.issue.editable = false}} property on the closed status # Configure a postfunction to trigger the {{Issue Closed}} event on the close transition # Trigger the {{Close}} transition # The Sprint field will be removed from the issue entirely. This does not happen when you have any other event configured, or not the editable property set up h3. Expected Results h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} ... {noformat} h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
The Sprint field value is removed on specific transition when using {{jira.issue.editable = false}} workflow property and Issue Closed event. h3. Steps to Reproduce # Create a board # Create a sprint (but do not start it) # Create an issue on the board and assign it to the Sprint # Configure a Workflow with the {{jira.issue.editable = false}} property on the closed status # Configure a postfunction to trigger the {{Issue Closed}} event on the close transition # Trigger the {{Close}} transition # The Sprint field will be removed from the issue entirely. This does not happen when you have any other event configured, or not the editable property set up h3. Expected Results Sprint field value remains as is. h3. Actual Results Sprint field value is removed upon transition. h3. Workaround Update the workflow post-function to use 'Issue Resolved' event. |
| Description |
Original:
Steps to reproduce:
* Create a board * Create a sprint (but do not start it) * Create an issue on the board and assign it to the Sprint * Configure a Workflow with the {{jira.issue.editable = false}} property on the closed status * Configure a postfunction to trigger the {{Issue Closed}} event on the close transition * Trigger the {{Close}} transition * The Sprint field will be removed from the issue entirely. This does not happen when you have any other event configured, or not the editable property set up |
New:
h3. Issue Summary
h3. Steps to Reproduce # Create a board # Create a sprint (but do not start it) # Create an issue on the board and assign it to the Sprint # Configure a Workflow with the {{jira.issue.editable = false}} property on the closed status # Configure a postfunction to trigger the {{Issue Closed}} event on the close transition # Trigger the {{Close}} transition # The Sprint field will be removed from the issue entirely. This does not happen when you have any other event configured, or not the editable property set up h3. Expected Results h3. Actual Results The below exception is thrown in the xxxxxxx.log file: {noformat} ... {noformat} h3. Workaround Required, if there is no workaround please state: Currently there is no known workaround for this behavior. A workaround will be added here when available |
| Minimum Version | New: 7.05 |
| Workflow | Original: JAC Bug Workflow v2 [ 2854615 ] | New: JAC Bug Workflow v3 [ 2935035 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Workflow | Original: JIRA Bug Workflow w Kanban v7 - Restricted [ 2546217 ] | New: JAC Bug Workflow v2 [ 2854615 ] |
| Status | Original: Open [ 1 ] | New: Needs Triage [ 10030 ] |
| Link | New: This issue relates to JSWSERVER-12281 [ JSWSERVER-12281 ] |