Hi @antoniokov, I just posted some details of what I’d like to accomplish with dependencies and visualization here:
General Feedback Request on Entity Scheduling and Dependencies
My use case is Project work that you could first plan with an anticipated schedule, then see how that schedule actually adjusts depending on changes to task dates within - if they finish later, or even ahead of schedule. Within these projects could be Features that are being built. The Features would be one type of entity in Fibery, with many tasks related that have to do with building the Feature successfully - dev task, review, QA, deployment.
So Ideally I’d like to be able to track on multiple levels here - one of the big pluses of Fibery vs. other apps:
- Track a project, for example “Launch new Functionality x to market” - which would involve building features, doing marketing, releasing content, communicating with existing users, etc. This is all “work” I will track in a few types of tasks, but I want the project to only show actual “work.” So the content pieces, the software features, since they are not “work” but rather “elements” that persist in my system, I’d like to track them elsewhere in Fibery.
- See a board of the Features I’m trying to develop. They will have tasks tracked in the Project I mentioned above - for example each will have a “dev task,” “review” etc. but they are not strictly work in the project.
So I’d like to track both the progress of the build of these Features in one area of Fibery, and the progress of the work that is needed to build them in another area, the “Project.”
To give just a bit more context, with Fibery I can track the actual “work” in a Feature Build this way with this “Project” entity, as opposed to taking the feature and moving it through a complex workflow to track it’s build, like I’d have to do in Jira or other strictly development tools. This is a big plus, because in reality if I have a project with cross-functional work, I don’t want a “feature,” that is actually not strictly speaking a “task,” in the same Project with task work, like “prepare marketing campaign” or “contact PR vendor,” because in reality they are not the same “type” of entity. Putting them together leads to inaccuracies in tracking work. And with Fibery I can avoid this!
I hope that’s clear and very eager for any help you can provide on what I can do now with Buttons, Formulas, and your API!