Post

1 follower Follow
0
Avatar

Umbrella Projects and visibility

Hi there,

 

Two questions:

Question 1 -

Sometimes I work with an Event Manager and for her there are usually multiple deliverable s with different due dates - but they all are under the same event. So, I will open the project (and consider that as my "Umbrella Project". So for example say our next event is a Holiday Party, I will open an Umbrella Project titled "Holiday Party" and from there I either open each deliverable as a task, milestone or even an indented sub project. Either way has been helpful in separating each of the deliverable s.

I depend on my homepage Projects View to keep me on track of whats due next and I have found myself missing some creeping due dates because the main project view only shows me the top tier project (which only provides the latest due date for that "umbrella" project.

How can I fix this view so that I can see any smaller projects dues dates that are also tied to these bigger "umbrella projects"

I have noticed when trying to manage the filter some fields called Parent or Parent Project, but do no see how I can open or label a project as a Parent or Parent Project...

 

Question 2 -

This question is about visibility I would like designers to have from the main project view for any individual milestone/task/sub project specs I upload at those specific pages...

i.e. a Designer clicks on "Holiday Party" and see's a list of deliverable s (whether they are listed out as separate tasks/milestones/sub projects - but instead of having to click on each of those to see their unique specs, is there a way see the specs/information directly from "Holiday Party" Project view ? Do you have a better suggestion on how I should go about this?

 

Satawneh Answered

Please sign in to leave a comment.

3 comments

0
Avatar

I would recommend using the Work Items or Projects (only in V6) modules to see ALL projects, regardless of whether they are a sub or parent project.  You can also set some filters here to help prioritize them.

As for question #2, can you describe what you mean by specs and whether your are on the V5.4 release or V6 (the V6 navigation is on the left)?

Josh Santos 0 votes
Comment actions Permalink
0
Avatar

Thanks Josh. I think your suggestion to use Work Item allows for me to see all the projects (both parent and "sub"). I didnt have much luck under the Projects view...

I am using V6

As for the specs question...

I just meant that for each sub project, I have specifications/sizes, briefs, information etc. I provide for the project to help the designer.

It makes sense to attach/store that information under its appropriate sub project task or milestone, but am worried a designer/resource wont see that information unless they dove directly into that specific sub project/task or milestone.

So with that said, it makes me wonder if I should provide all of the briefs at the parent project level. It is however annoying to have to attach the same stuff at the specific task/sub project/milestone level for the sake of consistency...

Satawneh 0 votes
Comment actions Permalink
0
Avatar

Ah, okay what you can do in V6 is create a view with the fields that designer will need and you can even toss in some sorts and filters along with the view.  That way they could quickly go through the project hierarchy along with the data they need without having to drill down into any specific items.  Have you tried customizing views yet?

Josh Santos 0 votes
Comment actions Permalink