| Reporter |
Dan Michaelson (danmichaelson)
|
|---|---|
| Created | Mar 15, 2013 8:59:16 PM |
| Updated | Mar 16, 2013 7:25:06 PM |
| Priority | Normal |
| Type | Bug |
| State | Open |
| Assignee | Vadim Gurov (vgurov) |
| Subsystem | Agile Board |
| Fix versions | No Fix versions |
| Fixed in builds | No Fixed in build |
| Affected versions | No Affected versions |
| Browser | Any Browser |
| OS | Any OS |
| Verified in build | Not verified |
| Verified by | Nobody |
| Reviewed by | No reviewed by |
| Severity | Routine |
What steps will reproduce the problem?
1. Open the subtask in RubyMine and tick "Mark In Progress". Screenshot 1 shows YouTrack before opening subtask 2 of BNS-27 in RubyMine.
2. Press reload in YouTrack. Screenshot 2 shows YouTrack after doing this.
What is the expected result?
No change in YouTrack.
What happens instead?
The parent issue (BNS-27 in my screenshot) moves to the Open column. It stays there even if I reload. I can put it back to the In Progress column to fix it.
But then if I close the subtask (mark it as fixed with a commit command in RubyMine), BNS-27 again goes back to the Open column (with a strikethrough on the subtask, as expected), and I again have to move it to In Progress. I have a hunch this bug probably occurs if you modify the subtask in any way, regardless of whether it's via the API etc.
1. Open the subtask in RubyMine and tick "Mark In Progress". Screenshot 1 shows YouTrack before opening subtask 2 of BNS-27 in RubyMine.
2. Press reload in YouTrack. Screenshot 2 shows YouTrack after doing this.
What is the expected result?
No change in YouTrack.
What happens instead?
The parent issue (BNS-27 in my screenshot) moves to the Open column. It stays there even if I reload. I can put it back to the In Progress column to fix it.
But then if I close the subtask (mark it as fixed with a commit command in RubyMine), BNS-27 again goes back to the Open column (with a strikethrough on the subtask, as expected), and I again have to move it to In Progress. I have a hunch this bug probably occurs if you modify the subtask in any way, regardless of whether it's via the API etc.