Large number of reviews - Collections?
1 1

8 posts in this topic

We use FTrack a little differently i think, than originally intended.  Basically we have a project per dept, w/objects under (aka sprints) and tasks assigned to those. They tend to get rather large, but that layout works really well for task tracking within the given team.


The problem comes in with reviews. We end up having to create a TON of them, and there's no way to generate folders or categories for the reviews to setup in. Let met give you an example...

Clients submit a project to our custom form, which then sends it into a project -> created a new object (CSProject) -> Generates a number of tasks under based on type . Basically EACH one of those objects is considered a project, and the tasks are the individual items. Each item gets its own Client Review.  The example included only shows 6 tasks, but ultimately we may have upwards of 300 tasks in there, all w/a need for their own client review.

 

So my questions are...

 

1) Is it possible to create a LIST of client reviews at the object level (like in the notes section or info) to create a task specific set of reviews?

2) Any way to organize the review list? 

3) Can the "Add to review" menu item list only the reviews associated w/a given object?

4) Can lists somehow drive the client reviews via name or connection on some level?
 

Appreciate the help! This is the last hurdle i'm having w/our CS team and usability. 

 

Cheers
Bryan

Share this post


Link to post
Share on other sites

Hi Bryan, thank you for the feedback and questions. This organizing part of the review system is built on the assumption that you have separate projects with a "limited" number of review sessions. Is there any way you could split up into more projects - or does that make things harder to overview and manage in other areas?

Are all of these 300 client reviews active at the same time? Could you be deleting some or do you need them for reference?

Otherwise it sounds like a feature request to having a way to categorise and organize the review sessions better.

Share this post


Link to post
Share on other sites

Not real way of limiting the number of projects unless there's a more overarching system in place for organizing the projects + single place to see all allocations. The original way we had it setup was that each request was a unique project.. which is pretty clean but very hard to organize across the dept and the project list gets really massive (and unwieldy). 

To combat that have made a single project w/subprojects which does work much much better from an organization standpoint. They aren't necessarily active at the same time but a significant list of them are. For instance, a request may have upwards of 20 items within it. Each item gets its own review... mainly because the client review system doesn't support the same in review organization as the internal reviews do. Something similar to the internal review system would potentially balance it out as we could then (most likely) make a review per project vs. task and organize them by name. 

We do delete old and unused client reviews, it is still just a rather large list.

Share this post


Link to post
Share on other sites
17 hours ago, pritchardhobe said:

Not real way of limiting the number of projects unless there's a more overarching system in place for organizing the projects + single place to see all allocations. The original way we had it setup was that each request was a unique project.. which is pretty clean but very hard to organize across the dept and the project list gets really massive (and unwieldy). 

Perhaps the new Studio overview is a step in the right direction. From there you can get a better overview of all ongoing projects.

Quote

To combat that have made a single project w/subprojects which does work much much better from an organization standpoint. They aren't necessarily active at the same time but a significant list of them are. For instance, a request may have upwards of 20 items within it. Each item gets its own review... mainly because the client review system doesn't support the same in review organization as the internal reviews do. Something similar to the internal review system would potentially balance it out as we could then (most likely) make a review per project vs. task and organize them by name. 

We do delete old and unused client reviews, it is still just a rather large list.

Thanks for elaborating, I will create a feature request of this and notify the team about the need to have better support for organizing client reviews. 

Share this post


Link to post
Share on other sites
On 10/02/2017 at 4:49 PM, pritchardhobe said:

I requested beta for it but haven't heard back yet.

Sorry about this, not sure why that happened! At the moment we're quite close to release so the cloud hosted beta period has ended.

Share this post


Link to post
Share on other sites

No worries. I figured that it was something like that. Is there an estimated release? Or even perhaps the ability to get a demo done of the upcoming features? I'd hate to buildout a whole new process if this will solve it all.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
1 1