Closed (fixed)
Project:
Storm
Version:
6.x-1.35
Component:
Storm Task
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
15 Feb 2011 at 11:50 UTC
Updated:
11 Mar 2011 at 23:51 UTC
Hi there
I have created organization, project, task and assigned it to a drupal user. after modifying module permissions, the user is able to see the task allotted to him but when edit is clicked it says "you dont have access to this page"..
Storm project: edit if assigned to project and Storm task: edit if assigned to task is set yes to authenticated user
Any thoughts where I am going wrong?
Comments
Comment #1
juliangb commentedThere are a few reports like this coming in at the moment, and ideally I'd like to be able to tackle them through automated tests in order that we can clarify exactly what's going on and guarantee that any fixes are not reintroduced in the future.
Would it be possible therefore to expand on your report a little please? It'd be ideal to have a step by step guide to reproducing the bug from a clean install - i.e. add organization A, project B, task C. Assign user D to task C... also to confirm the expected and current outcomes.
Comment #2
kumarangopi commentedJulian:
Thanks for your reply. I followed these steps:
1. Installed Storm module
2. Enabled it
3. Created organization
4. Created Drupal user
5. Created Team
6. Created Project
5. Created task and assigned project manager and user account
7. changed storm permissions
8. Logged in as user, able to see the task
9. But when clicked to edit, it says you don't have access to that page
Is that helpful?
Comment #3
juliangb commentedWould you be able to list all of the permissions the user has? I assume it isn't just the edit permissions if the user can see the task?
Comment #4
kumarangopi commentedJulian:
User is able to see the task but not able to edit. Here is the permissions scenario:
I have created an administrator role and admin user belongs to that role. So here authenticated users are nothing but drupal user accounts only.
I have checked(enabled) the following check boxes for authenticated users:
storm module:
Storm: access administration pages
Storm: access dashboard
stormorganization module
Storm organization: access
stormproject module
Storm project: access
Storm project: edit if assigned to project
Storm project: edit if project manager
Storm project: edit own
Storm project: view if assigned to project
Storm project: view if project manager
Storm project: view own
stormtask module
Storm task: access
Storm task: add
Storm task: edit all
Storm task: edit if assigned to task
Storm task: edit own
Storm task: view if assigned to task
Storm task: view own
Does this helps? I appreciate your patience in replying
Comment #5
kumarangopi commentedJulian:
I believe I got it. User is able to edit the task now. But he can edit the dates, everything? ):
Can't we make that he edit only status?
Thanks for your help
Comment #6
juliangb commentedOut of interest, what did you change to enable editing of the task?
There is only one level of edit permissions - edit or not. If you want to do more than this then currently you need to write a small custom module implementing hook_form_alter - then you can set #access to false on the form items you don't want them to edit.
Comment #7
kumarangopi commentedJulian:
Thanks for your reply, I shall try it. I think the issue was previously authenticated user was not enabled to edit the node content. Tasks, Projects and all are seems to be nodes. Since node content edit permission was not given to user, user was not able to edit the task. I believe that this is the reason.
Comment #8
juliangb commentedGreat, sounds like this is solved. Please reopen if you have further questions.
Comment #9
kerby70 commentedI found my "Storm User" profile needed the filter module: administer filters permission turned on to edit any task.
Comment #10
juliangb commented@Kerby70, I would strongly suggest against giving the administer filters permission to untrusted users. If you are having trouble editing tasks without this permission, please open a new support request and we can work through the problem.