Actions
Bug #4487
closed[Workbench] Users shouldn't have the option to "Remove selected" when they don't have the proper permissions
Status:
Resolved
Priority:
Normal
Assigned To:
Radhika Chippada
Category:
Workbench
Target version:
Story points:
0.5
Description
Files
Updated by Tim Pierce about 10 years ago
- Subject changed from Users shouldn't have the option to "Remove selected" when they don't have the proper permissions to [Workbench] Users shouldn't have the option to "Remove selected" when they don't have the proper permissions
- Category set to Workbench
- Target version set to Bug Triage
Updated by Radhika Chippada about 10 years ago
- Status changed from New to In Progress
- Assigned To set to Radhika Chippada
Updated by Radhika Chippada about 10 years ago
- Target version changed from Bug Triage to 2014-12-10 sprint
Updated by Brett Smith about 10 years ago
- Target version changed from 2014-12-10 sprint to Bug Triage
Reviewing 95fd4dd
- In the view, you can just call
@object.editable?
to check if the user has write permission. That covers all the corner cases and will save you some typing. - In the new test, the name has a typo "avaialble."
- In the test, please go directly to the project page:
visit page_with_token("active", "/projects/#{my_project['uuid']"})
. In general, being more conscientious about what pages we visit in integration tests will help keep test runtimes proportional what we're testing. - The two
assert_no_selector
lines are redundant. Just checkingli
is fine; it will findli.disabled
if that exists. Given this, it might make sense to have all the tests look forli
.
Thanks.
Updated by Brett Smith about 10 years ago
- Target version changed from Bug Triage to 2014-12-10 sprint
Updated by Radhika Chippada about 10 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset arvados|commit:46aee7d3bec5676e054bddc38633b2775f3a0fd6.
Actions