rk@tigase.net opened 22 hours ago
-
Previous Value Current Value Open
In Progress
-
rksuma@Ramakrishnans-MacBook-Pro sztab % git add backend/src/main/java/com/sztab/dto/issue/IssueUpdateDto.java \ backend/src/main/java/com/sztab/service/impl/IssueServiceImpl.java \ backend/src/test/java/com/sztab/service/IssueServiceImplTest.java git commit -m "SZ-147: Couple assignee and state fields - setting assignee auto-transitions to ASSIGNED, clearing reverts to NEW" git push origin wolnosc [wolnosc 7e5a609] SZ-147: Couple assignee and state fields - setting assignee auto-transitions to ASSIGNED, clearing reverts to NEW 3 files changed, 90 insertions(+), 21 deletions(-) Enumerating objects: 37, done. Counting objects: 100% (37/37), done. Delta compression using up to 12 threads Compressing objects: 100% (16/16), done. Writing objects: 100% (20/20), 3.05 KiB | 3.05 MiB/s, done. Total 20 (delta 10), reused 0 (delta 0), pack-reused 0 (from 0) To https://tigase.dev/sztab.git de84677..7e5a609 wolnosc -> wolnosc rksuma@Ramakrishnans-MacBook-Pro sztab % -
Previous Value Current Value In Progress
Closed
| Type |
Bug
|
| Priority |
Normal
|
| Assignee | |
| Version |
1.10.1
|
| Sprints |
n/a
|
| Customer |
n/a
|
Issue Votes (0)
Watchers (2)
Problem Setting an assignee on an issue does not automatically transition state to ASSIGNED. This allows an inconsistent state — issue in NEW with an assignee, or ASSIGNED with no assignee.
Expected behavior
Setting assignee => auto-transition to ASSIGNED state Clearing assignee => auto-transition back to NEW Setting state to ASSIGNED => assignee field becomes required
This is a breakage of issue workflow.