Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0016226 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Mantis @ OB] Others | major | have not tried | 2011-03-11 07:50 | 2011-03-11 07:50 | |||||||
| Reporter | alostale | View Status | public | |||||||||
| Assigned To | staffrm | |||||||||||
| Priority | normal | Resolution | open | |||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | |||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Review Assigned To | ||||||||||||
| Summary | 0016226: Incorrect issue assignment when creating backport | |||||||||||
| Description | When scheduling it is possible to create a backport and reassign the issue to another developer. If both actions are performed at the same time, the original issue is assigned to the new person, but the new backport remains assigned to the original one. | |||||||||||
| Steps To Reproduce | -Report a new issue -Click on schedule -Select a backport, change the assignee and execute -Check the original issue is correctly assigned but the new one is assigned to the original person | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2011-03-11 07:50 | alostale | New Issue | |
| 2011-03-11 07:50 | alostale | Assigned To | => staffrm |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |