Teammember list doesn't contain persons assigned
cyc - May 21, 2009 - 10:42
| Project: | Storm |
| Version: | 6.x-1.22 |
| Component: | Storm Teammember |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Description
as in the title.
storm/teammembers page have only organization, project, task & ticket columns, but not person
the result is you don't know which record refers to which person
#1
+1 list does need to include more info about the actual person who is a team member to be most useful. not sure i would call it a bug though - i looked through the code and there is no provision for this right now. so it's acting as expected, just not as desired.
#2
@cglusky:
lol
tell me the purpose of the list where all items looks identical;-)
maybe you know the secret how to distinguish them, but I'm not..
#3
@cyc - yeah, not easy to do. i guess it would be a feature request in my book, but that's just splitting hairs as they say.
i have spent the last week hacking on OG with a bunch of cck node references and views to get something i can use. i really like the out-of-the-box concept of Storm and @magnitiy is clearly working hard on it, but i need more flexibility. but if Storm meets your needs i would recommend it over the last week i just spent doing it the "drupal way" with cck and views.
r,
c
#4
Re #2 - i'm afraid if you don't know the secret then I can't tell you.
On a more serious note... i'm going to be looking at a whole raft of teammember bits soon - and so i'll be looking at this as part of that.
#5
subscribing.
I have just discovered Storm and I'm configuring it for our needs -- I'm trying to resist the urge to use CCK to associate users to projects as team leads, team members, etc, because of the promise of the integrated TeamMember functionality . . . but as it stands right now it's hard to figure out how to use what's there.
-j
#6
i have seen that this issue is priority:
#464352: Priorities before next stable release
so have made a patch. if i understood problem correctly - it is working.
try and report.
patch is against last dev (2009-Jun-29). from "modules" directory:
patch -p0 -i teammember_person.patch#7
Thanks for this - bit confused by the changes to the stormteammember.js file - are the sections that are added but commented out needed - and if not - does this function actually need to change at all?
#8
changes in .js are not needed. it is better to leave them out. i was also confused with that, so i was trying to make Person filter dependable of Organization and Project selections (like tickets and tasks).
but after i have done some work i realized that user may want to see everything for some Person (i would need that), without using filters.
so no needs for changing stormticket.js, for now - there may be problem if there are to many Persons involved in all projects, or that there are to many Organizations for simple selection list, but that's another story.
so here is new and reviewed patch, without any changes to stormticket.
#9
I was wondering if any of you can make another patch that shows "People/Person" column in Task list.
Also, could someone tell me where/how I can set Tasks page to list all the tasks instead of just first 10?
I and my team would really appreciate it.
#10
Committed (with a couple of ammendments)
http://drupal.org/cvs?commit=232180
@Kamikaze - it sounds like your points are unrelated to this issue - please open a new issue.
#11
I am impressed with Storm module, but I would like to make a request.
Could someone make a patch that shows "Person/People" column in Tasks?
Also if another can be made, I would like to see "Project Manager" column show in Projects.
That will be great.
#12
@Kamilkaze, the link to create a new issue is http://drupal.org/node/add/project-issue/storm.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.