Project

General

Profile

Defect #1232

Once Pending Effort field is set to empty it cannot be changed any more

Added by Bartosz Firyn over 7 years ago. Updated over 7 years ago.

Status:
Rejected
Priority:
Normal
Category:
General
Target version:
-
Source:
Development
Detected on version:
Blocked:
No
Alone:
Milestones:
Sprint:

Description

Hi,

The problematic scenario is the following:

  • Create new issue and leave "Pending Effort" field empty
  • Save it by clicking on "Create" button
  • Edit issue and change "Pending Effort" from empty to 20
  • Save it by clicking on "Submit" button
  • Observe:
    • The "Pending Effort" field was not updated to 20 and it's still empty (not expected).

The only solution for this is to delete such issue and re-create it again.


Files

1.png (35.1 KB) 1.png Bartosz Firyn, 2016-12-02 17:22
2.png (34.8 KB) 2.png Bartosz Firyn, 2016-12-02 17:22
3.png (35.7 KB) 3.png Bartosz Firyn, 2016-12-02 17:22
4.png (39.3 KB) 4.png Bartosz Firyn, 2016-12-02 17:27
#1

Updated by Emilio González Montaña over 7 years ago

  • Status changed from New to Rejected

I've tested but with current version it's not failing...

#2

Updated by Bartosz Firyn over 7 years ago

Hi Emilio,

This problem exists. Let me clarify in more details what are the steps required.

  1. Create task and put it in the next sprint (not backlog and not empty field). This is important. You have to put it in the next sprint since if you create task in backlog or leave sprint empty, then everything works fine. I was testing on a sprint which start in next 3 days.
  2. Provide no Pending Effort field and leave Pending Effort field empty.
  3. Save
  4. Edit issue and modify Pending Effort (to e.g. 1),
  5. Save
  6. Observe:
    • Pending Effort field is not updated from empty to 1.
    • No history modification is present.
#3

Updated by Bartosz Firyn over 7 years ago

Just FYI, I testes several combinations and only these where I assign to next sprint are failing.

#4

Updated by Bartosz Firyn over 7 years ago

I just tested v0.16.1 and I confirm that problem is still present.

Also available in: Atom PDF