Openbravo Issue Tracking System - Mantis @ OB
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0030065Mantis @ OBOtherspublic2015-06-01 14:142015-06-01 14:14
Reporteralostale 
Assigned Tostaffrm 
PrioritynormalSeverityminorReproducibilityalways
StatusnewResolutionopen 
PlatformOS5OS Version
Merge Request Status
Review Assigned To
OBNetwork customer
Summary0030065: backport creation while scheduling process sets originally assigned user instead of scheduled one
DescriptionConsider the following flow:

1. a new issue is reported, it gets assigned to default generic team triage user
2. during triage it turns out it requires to be backported

step 2 requires of 5 actions:
2.1 assign the issue to the developer who is going to work on it
2.3 mark the issue as scheduled
2.2 create the backports
2.4 assign the issue to the developer who is going to work on it which is usually the same one that is going to work in the original issue
2.5 mark the backports as scheduled

these 5 actions can be done using the Change status to scheduled button


The problem is Change status to scheduled button does all the actions but 2.4 so the backports are assigned to the developer that was originally assigned to the issue (in this case the team's generic one) and not the new one.
Steps To Reproduce1. Create a new issue ERP issue with Platform category
   - it is automatically assigned to platform user -> OK
2. Click in the Change status to scheduled button
3. Assign it to a developer (ie. alostale) and mark a backport to be created
   - the original issue is scheduled and assigned to alostale -> OK
   - the backport is assigned to platform user -> NO OK: expected to be assigned to alostale
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2015-06-01 14:14alostaleNew Issue
2015-06-01 14:14alostaleAssigned To => staffrm

There are no notes attached to this issue.