Content
View differences
Updated by Robin Wagner over 5 years ago
### **Environment**:
qa-stage
Firefox
### **Steps to reproduce:**
1. Set up parent project with action board (subprojects) and add subprojects as columns.
2. Sign in as user with permission to access parent project but not subproject(s).
### **Actual Behavior**
Error message is shown indicating that there is an error (with option to remove column).
This can be quite confusing for a user: It can easily happen that a user removes the columns (clicking on the link) and thereby changing the boards view for other users as well.
<figure class="image"><img src="/api/v3/attachments/19337/content"></figure>
### **Expected Behavior**
We could either show a different (more descriptive) warning message or not show the project columns at all.
For consistency reasons, I'd suggest we do not show the project columns if a user has no permissions (consistent to behavior on e.g. work package page (e.g. when displaying work packages from subprojects in query)).
qa-stage
Firefox
### **Steps to reproduce:**
1. Set up parent project with action board (subprojects) and add subprojects as columns.
2. Sign in as user with permission to access parent project but not subproject(s).
### **Actual Behavior**
Error message is shown indicating that there is an error (with option to remove column).
This can be quite confusing for a user: It can easily happen that a user removes the columns (clicking on the link) and thereby changing the boards view for other users as well.
<figure class="image"><img src="/api/v3/attachments/19337/content"></figure>
### **Expected Behavior**
We could either show a different (more descriptive) warning message or not show the project columns at all.
For consistency reasons, I'd suggest we do not show the project columns if a user has no permissions (consistent to behavior on e.g. work package page (e.g. when displaying work packages from subprojects in query)).