-
Bug
-
Resolution: Timed out
-
Low
-
1
-
Severity 3 - Minor
-
1
-
Issue Summary
Story points field does not allow populating a negative value to the field. The following error is seen when trying to update a negative value to the Story Points field:
Time for some positivity. Story point estimates can't be negative.
However, it is possible to populate a negative Story Points field value if the update is made via CSV import or Rest API.
Steps to Reproduce
- Import a story issue to a project via CSV wherein the file has a negative value set for the "Story Points" field
Summary, Story Poits test, -100000000
(or)
- Run an "Edit issue" API call to update the story points field with a negative value.
curl --request PUT \ --url 'https://instancename.atlassian.net/rest/api/latest/issue/{{issuekey}}' \ --user '<email>:<API>' \ --header 'Accept: application/json' \ --header 'Content-Type: application/json' \ --data '{ "fields": { "customfield_10024": -50 } }'
Expected Results
The story points field should not allow negative field values to be stored via CSV or API, similar to UI behavior.
Actual Results
The Story Points field value is updated with a negative value via CSV or API.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JRACLOUD-93742 Negative Story Points should not be allowed
-
- Short Term Backlog
-