Closed (fixed)
Project:
Storm
Version:
6.x-1.x-dev
Component:
Storm Task
Priority:
Normal
Category:
Bug report
Assigned:
Issue tags:
Reporter:
Created:
30 Mar 2011 at 20:55 UTC
Updated:
3 Jan 2014 at 02:58 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
chertzogI was trying to think of a way around this issue, when i struck me that when the user looks at their tasks from the dashboard, everything is displayed correctly. Its just a views views permission issue that the problem, so why not exclude views from the equation?
How would you go about creating a block that just displays the task listing? Would it be as easy as pasting part of the stormtask.theme.inc into a block and seeting the input format to PHP code?
Im not skilled enough in this to do it and i get lost here: http://drupal.org/node/745356 with the argument issue.
Comment #2
juliangb commentedViews is a much better way to go rather than entering PHP code into a block.
Unfortunately I have limited time to assist at the moment but will do so when I can.
Can you assist by posting a very detailed step by step way to reproduce the original bug starting from a fresh Storm installation? If I can follow this exactly, it will help for me to reproduce, debug and fix.
Comment #3
chertzogOk, here are the steps:
STORM:
1. Clean install of Drupal 6.20
2. install Storm 6.x-2.x-dev and Views 6.x-2.11
3. Create role for employees that has the folowing permissions:
a. access content
b. Storm: access dashboard
c. Storm organization: access
d. Storm organization: view belonged
e. Storm person: view own
f. Storm project: access
g. Storm project: view if assigned to project
h. Storm task: view if assigned to task
i. Storm task: edit if assigned to task
j. Storm team: view belonged
k. access all views
4. Create role for manager that has the folowing permissions:
a. access content
b. Storm: access dashboard
c. Storm organization: access
d. Storm organization: view belonged
e. Storm person: view own
f. Storm project: access
g. Storm project: view if assigned to project
h. Storm task: access
i. Storm task: add
j. Storm task: edit if assigned to task
k. Storm task: edit own
l. Storm task: view if assigned to task
m. Storm task: view own
n. Storm team: view belonged
o. access all views
5. Create drupal users with respective roles.
a. Manager1
b. Manager2
b. Employee1
c. Employee2
6. Create organizations: ORG-1, ORG-2
7. Create Storm People for the users, associating their drupal user.
8. Assign Manager1, Employee1 to Org-1, and Manager2, Empoyee2 to Org-2.
9. Create Team1, with members, Employee1, Employee2, and Manager1. Yes is is a cross organization team.
10. Create Project1 under Org1, Project manager is Manager1, and Assigned to is Team1.
11. In Project 1, Create Task 1 and Task 2 and assign them to Employee1 and Employee2 respectively.
VIEWS:
1. Create My_Tasks View (attached)
BLOCKS:
1. Add My Tasks Block to right Sidebar (Garland Default Theme)
----------------------------
With the above configuration, i would expect that when the employees log in, they would see a block in the right sidebar with the tasks they are assigned to. But when they log in, there is nothing there, but if they click on tasks through /storm/tasks/, they see they ones they are assigned to. They also only see their tasks when they click on the tasks button from the project page.
--------------------------
If i give the employee role, the "Storm task: view of user organization" permission, Employee 1 sees all tasks both in the block, and the /storm/tasks/, and Employee2 sees only tasks assigned to employee1 in the block view, but sees their own in through the /storm/tasks/. Which is wierd.
If i take away the "Storm task: view of user organization", and give them the "Storm task: view all" permission, they see everything (as expected)
Comment #4
chertzogI'm guessing this will be fixed when #889610: List pages to be default views is implemented.
Comment #5
juliangb commentedThis will be a blocker for that issue.
The views integration is an area I am very interested in getting solved, but I don't have the time right now to push it forward.
Comment #6
juliangb commentedReverting title
Comment #7
juliangb commentedI've reproduced and confirmed this bug. (Note to self - test site 002bw).
Am looking into it, currently unsure as to what is going on.
Comment #8
juliangb commentedI think this patch might solve the issue, needs testing.
Comment #9
juliangb commentedTagging
Comment #10
juliangb commentedThat gave errors - but I think this one works.
Comment #11
juliangb commentedCommitted to 2.x.
Patch for 1.x.
Comment #12
juliangb commentedComment #13
juliangb commentedCommitted to 1.x.