Content
View differences
Updated by Niels Lindenthal over 6 years ago
## rst First bug report by Robin
### **Steps to reproduce:**
1. Add a table of related work packages group to a work package type.
2. In the table of related work packages display work packages which are "required by".
3. Go to a work package of that type, click to add a new entry and create a work package.
### **Actual Behavior**
Work package has relation type "Required" instead of "Required by", meaning the created work package is not displayed in the table (see gif).
### **Expected Behavior**
Work package is correctly added with relationship "required by".
## Second bug report from Niels
The labels are inconsistent and misleading:
<table><tbody><tr><td><strong>Relations tab</strong></td><td><strong>Form configuration</strong></td><td></td></tr><tr><td>Requires</td><td></td><td>a work package created in the embedded table ends up swapped in the counterpart (PR 8023)</td></tr><tr><td>Required by</td><td></td><td>a work package created in the embedded table ends up swapped in the counterpart (PR 8023)</td></tr><tr><td>Part of</td><td>Including</td><td></td></tr><tr><td>Includes</td><td>Beeing part of</td><td></td></tr><tr><td>Blocks</td><td>Blocked by</td><td></td></tr><tr><td>Blocked by</td><td>Blocking</td><td></td></tr><tr><td>Duplicated by</td><td>Duplicating</td><td></td></tr><tr><td>Related to</td><td>Relating to</td><td></td></tr><tr><td>Precedes</td><td>Following</td><td></td></tr><tr><td>Follows</td><td>Preceding</td><td></td></tr><tr><td>Children</td><td>Being child of</td><td></td></tr></tbody></table>
I suggest to use the same wording in both select fields:
The label above the relations table configuration would be like this:
Header: Add table of related work packages (existing translation string from create button)
Filtered work package relations (new translation string)
###
### **Steps to reproduce:**
1. Add a table of related work packages group to a work package type.
2. In the table of related work packages display work packages which are "required by".
3. Go to a work package of that type, click to add a new entry and create a work package.
### **Actual Behavior**
Work package has relation type "Required" instead of "Required by", meaning the created work package is not displayed in the table (see gif).
### **Expected Behavior**
Work package is correctly added with relationship "required by".
The labels are inconsistent and misleading:
<table><tbody><tr><td><strong>Relations tab</strong></td><td><strong>Form configuration</strong></td><td></td></tr><tr><td>Requires</td><td></td><td>a work package created in the embedded table ends up swapped in the counterpart (PR 8023)</td></tr><tr><td>Required by</td><td></td><td>a work package created in the embedded table ends up swapped in the counterpart (PR 8023)</td></tr><tr><td>Part of</td><td>Including</td><td></td></tr><tr><td>Includes</td><td>Beeing part of</td><td></td></tr><tr><td>Blocks</td><td>Blocked by</td><td></td></tr><tr><td>Blocked by</td><td>Blocking</td><td></td></tr><tr><td>Duplicated by</td><td>Duplicating</td><td></td></tr><tr><td>Related to</td><td>Relating to</td><td></td></tr><tr><td>Precedes</td><td>Following</td><td></td></tr><tr><td>Follows</td><td>Preceding</td><td></td></tr><tr><td>Children</td><td>Being child of</td><td></td></tr></tbody></table>
I suggest to use the same wording in both select fields:
The label above the relations table configuration would be like this:
Header: Add table of related work packages (existing translation string from create button)
Filtered work package relations (new translation string)
