-
Bug
-
Resolution: Won't Do
-
Low
-
None
-
Minor
-
Jira Software
Issue Summary
When attempting to edit the story points field to a negative value using the UI an error will appear blocking the update. However, if this is done via automation, the field can indeed be set to a negative value.
Steps to Reproduce
- Create an automation rule with an "Issue created" Trigger for example
- Add an action to edit the story points field with a negative value
Expected Results
Generate an error message to prevent the input of negative values. Below is the error message from the UI.
Actual Results
The story points field will be updated with a negative value and the history will show that automation updated the field to Zero:
Workaround
To avoid the issue, add a condition in the automation rule that updates the story points field to zero if a negative value is attempted.
- is related to
-
-
- Needs Triage
-
[AUTO-1012] Story points accepting negative value using automation rule
| Link | New: This issue is related to JRACLOUD-93742 [ JRACLOUD-93742 ] |
| Resolution | New: Won't Do [ 10000 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
Confirmed bug - tested locally just now. Moving to Gathering Impact to allow future cases to be linked, to ascertain the User Impact Score.
| Description |
Original:
h3. Issue Summary
When attempting to edit the story points field to a negative value using the UI an error will appear and the update cannot be done, however, using the automation, the story points field can result in a negative value. h3. Steps to Reproduce # Create an automation rule with an "Issue created" Trigger for example # Add an action to edit the story points field with a negative value !image-2023-12-05-09-19-39-194.png|width=485,height=166! h3. Expected Results An error message preventing negative values: !image-2023-12-05-09-20-45-671.png|width=451,height=67! h3. Actual Results The story points field will be updated with a negative value and the history will show that automation updated the field to Zero: !image-2023-12-05-09-23-58-540.png|width=506,height=97! h3. Workaround Add a condition in the automation rule to update the Story points field to zero if the value is negative. |
New:
h3. Issue Summary
When attempting to edit the story points field to a negative value using the UI an error will appear blocking the update. However, if this is done via automation, the field can indeed be set to a negative value. h3. Steps to Reproduce # Create an automation rule with an "Issue created" Trigger for example # Add an action to edit the story points field with a negative value !image-2023-12-05-09-19-39-194.png|width=485,height=166! h3. Expected Results Generate an error message to prevent the input of negative values. Below is the error message from the UI. !image-2023-12-05-09-20-45-671.png|width=451,height=67! h3. Actual Results The story points field will be updated with a negative value and the history will show that automation updated the field to Zero: !image-2023-12-05-09-23-58-540.png|width=506,height=97! h3. Workaround To avoid the issue, add a condition in the automation rule that updates the story points field to zero if a negative value is attempted. |
After more investigation, it turns out the problem is in the Jira REST API layer, which allows negative story point values. So it's only a front-end validation on the Jira side that recommends against negative SP values, but doesn't restrict them.
If they are to be restricted, then the REST API needs to restrict them, and that will also fix this too since Automation relies on the REST API call. This would required an improvement/bug ticket for the Jira REST API team.