BigPicture 8.34 update visualized with examples

Поділитися
Вставка
  • Опубліковано 21 жов 2024
  • This update brings you one very cool feature and several other updates that are less impressive, but still quite useful. Check out what's what inside the video :) Enjoy!
    -------------
    Save yourself the trouble of discovering all the pitfalls or non-standard use cases of this amazing tool. Reach out to us, we will help you get rolling with BigPicture in just a couple of days!
    ► info@geniusgecko.com
    -------------
    Check out our BigPicture Training. Boost your PMO performance!
    ► geniusgecko.co...
    If you have any questions, feel free to contact us:
    ► info@geniusgecko.com
    ► geniusgecko.co...
    🔔 Subscribe to our channel.
    Do you want to know more about us? Find us on social media!
    ► LinkedIn: / genius-gecko-jira-apps...
    ► Facebook: / jiratraining
    #projectmanagement #bigpicture #portfoliomanagement #riskmanagement #bigpicturetraining

КОМЕНТАРІ • 6

  • @anjabuckley2351
    @anjabuckley2351 3 місяці тому +1

    Do you happen to know where to find the expand all / collapse all feature? The Big Picture documentation states it is under "data" but I cannot find it anywhere and it is also not visible in the data drop down menu in your tutorial (02:08). Thanks in advance :)

    • @geniusgecko-project-management
      @geniusgecko-project-management  3 місяці тому +1

      Use the small tick next to the column name that has the hierarchy indicator. Basically the same one you use to expand/collapse on the issue level, but it's also next to one of the column names (the one that is marker as a root column in the column views configuration)

    • @anjabuckley2351
      @anjabuckley2351 3 місяці тому

      ​@@geniusgecko-project-management Thank you very much for your prompt response and assistance.

    • @geniusgecko-project-management
      @geniusgecko-project-management  3 місяці тому

      @@anjabuckley2351 You're welcome :)

  • @DaveMathijs
    @DaveMathijs 4 місяці тому

    Shouldn't it be called "Parent Box" rather than "Sub-Box"?

    • @geniusgecko-project-management
      @geniusgecko-project-management  4 місяці тому

      An interesting question. I can see how this also makes sense, but I didn't think about it earlier, which means that for me probably sub-box is more intuitive. It's because I imagine that this will be used to see which sub-boxes of the current box in context the issues belong to. When I think about it like this, it will never be a parent box. I'm not sure if there's a literal that covers both approaches. Maybe simply "Box" :)