¿Con qué podemos ayudarte?

Por ejemplo Diagramas de Gantt, Crear tareas, Compartir carpetas

Blog

Task Based Reports - Parent Folder vs Parent Project Grouping

3 comentarios

  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Rikard Karlsson

    I agree, I have a similar challenge. I have a structure as : Customer Projects(Folder)/%Company%(Folder)/%Project%(Project)/%task%. To be able to extract all timelogs and figure out to which client it relates to, its a hard job. This work would be so much easy if the entire Parent Folder tree were displayed in the report.

    Is this helpful? 2
    Acciones de comentarios Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Francesco Alessi

    I think I agree, however... what may work better is to have the ability to mark folders as a "report level."  The reason I say this is because everyone's structure is a little different.  While doing a 1-up, 2-up, 3-up grouping or filter would work in a lot of cases.  There would be some where things would still show oddly.

    For example:

    2018

    >Main client
    >>Section client

    >>>Team client
    ....Project

    >>>>team 1

    ------task 1

    ------task 2

    >>>>team 2

    ------task 1

    ------task 2

     

    >Main client

    ....Project

     

    ------task 1

    ------task 2

     

    >Main client

    >>Section client

    >>>Team client

    ....Project

     

    ------task 1

    ------task 2

    So if I was doing a report on tasks... and I wanted to see the parent folder 1-up, I would get 3 different results
    1. Project level
    2. Team client

    3. Main client

    So if we had a way of tagging a folder for reporting.  So maybe I know I have up to 5 levels of reporting.  So I could designate the main client as report level 2, and the sectional client as 3, and the team client as 4, and the the team as 5...  So if I wanted the report to show my Main Client level, I just tell it level 2, if I want to see the team client level then I would pick level 4.  If those levels are missing, then it would be awesome to be able to build in logic so where we could tell the system if it's missing to use the next level up or down from the level chosen, but not to go lower than 1 level above the task.  So if we pick to report on level 3 say... but it's missing on some projects because of the way the structure is built, I may choose to report those items as is, or maybe 1 level up, or 1 level down.

    I'm in favor of what you are asking, just wondering if it could be more powerful.

    Is this helpful? 1
    Acciones de comentarios Permalink
  • Spot On! 👍 Innovative Approach 💡 Stellar Advice 💪
    Avatar
    Stephen

    Hey 👋 

    I have an update on this request. It's Structured (or Hierarchy) Reports. Now, in Reports, you can see subtasks under their parent tasks and parent tasks under the Folders or Projects.

    You can read more about this, and provide your feedback here 👍

    Thanks for offering use-cases, votes and examples here!

    Stephen Community Team at Wrike 💡Infórmate sobre las funciones y prácticas recomendadas de Wrike

    Is this helpful? 0
    Acciones de comentarios Permalink

Iniciar sesión para dejar un comentario.

Folllowing List for Post: Task Based Reports - Parent Folder vs Parent Project Grouping
[this list is visible for admins and agents only]

Community

Welcome 🖖

Hi there! 🙂 Want to become a black belt Wrike Ninja? Here's how to earn a Wrike badge

Welcome 🖖 Have you checked out this week's Release Notes yet?

Hey! 👋 Curious about something? Visit How To to search and ask the Community for answers.

Welcome! 👋 Figured out a good tip or trick? Share it in Best Practices.

Want to connect your existing software to Wrike? Learn and ask how in the API section.