Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

This question is no longer available

Deleted user November 12, 2019

Nothing here to display

1 answer

0 votes
Paul Mata November 26, 2019

I will assume you have a valid business case for trying to clear the time spent if you enter a time greater than the original estimate (although, I can't imagine what it is but that's beside the point). I did some investigation this morning and found a few problems that need to be addressed.

  • When I used the JSON that you show above in the advanced editor, I was getting errors. I plugged that JSON into JSONLint to validate it and found a few errors. The correctly formatted JSON is:
{
"fields": {
"timetracking": {
"timeSpentSeconds": "0"
}
}
}
  •  Note that I changed the field you're editing to "timeSpentSeconds"
    • When I put in the correctly formatted JSON using "timeSpent" an error was returned in the audit log that indicated that field is not able to be edited directly.

This also does not clear the aggregated time spent on the task, it actually clears the original estimate. I can't find a way to actually accomplish what you were attempting to do (probably because the time spent working on an issue is never meant to be cleared).

timeSpentSeconds.PNG

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events