Leaderboard


Popular Content

Showing most liked content since 05/22/2018 in all areas

  1. 5 points
    We find the 'old' documentation invaluable for sharing and training internally. The new docs simply aren't suitable (at least not yet). We miss the ability to: Link to specific sub-sections. Access the docs offline. Navigate left and right through a topic. Link to the specific release documentation (as we are often behind latest by a few versions). Link directly to API reference (via intersphinx) from our API reference and then maintain context in surrounding docs. Please bring back the 'old' docs or at least keep updating them alongside the new ones until you can support all these features in the new docs.
  2. 1 point
    Agree. I find the old docs much clearer and easier to navigate.
  3. 1 point
    ewokninja

    Time Zone Support

    Being part of a company that has users in multiple time zones it would be very convenient to be able to specify a time zone for any date/time field.
  4. 1 point
    Mattias Lagergren

    Time logging

    Thank you for reporting, I was not aware of this and at the moment we've restricted time-logging to task and this sounds like a bug.
  5. 1 point
    Thanks for sharing, I like the idea. This has been on our radar previously so it's nice to see a demand for it.
  6. 1 point
    Nice mockup! I would suggest for backend, that we can reference git repository online and offline for this.
  7. 1 point
    We'd like to be able to apply a View across multiple/all projects with the functionality to export as well.
  8. 1 point
    Afaik this is not documented. The ftrack-python-api hides this in convenience method and the user never has to understand this part, but for the javascript API things are more hands-on. I will raise this question with the team.