Hi, We're really enjoying using Quire, however I have one feature suggestion: shared tasks between projects. One of the things we're trying to communicate in the course of planning and prioritizing a project is shared dependencies.
Like for example if you were a highly organized sandwich shop you might have 2 projects: "Peanut Butter and Jelly Sandwich" and "Ham and Cheese Sandwich" that both share a dependent subtask called "Bake Bread". š
Understanding shared dependencies between projects is often useful in that it helps to prioritize the shared tasks if you understand the number of projects that depend on them.
In my contrived example above, should the sandwich shop also decide to serve tomato soup (because the owner's wife loves soup) you might still want to prioritize baking bread over soup-related tasks because maybe there are 25 sandwich projects that depend on the "Bake Bread" task.
Thanks for making a great application.
āļø I have merged your post with this post #277 already covering this request. Feel free to add your comments to that thread.
Peggy, Jan 22, 2021
Hi Crystal, That's a really interesting idea. How would you remove a reference to a dependent task? Would you have to delete the #BakeBread from the comment? I really like the idea of being able to inspect the common "Bake Bread" task and see what other tasks/projects it's referenced from.
Alternately, maybe you could link a dependent task by using the hashtag format in the title of a subtask? For example: if I'm looking at my "Grilled Cheese Sandwich" project and I add a subtask with the title "#BakeBread" perhaps that could serve the same purpose. It might also make it easier to see at a glance what dependencies a project relies on without having to search through the comments section.
e.g. Project: Grilled Cheese Sandwich
- #BakeBread
- Heat frying pan
- Butter 2 slices of bread
- etc.
Matt Kopit, Jun 14, 2018
Hi Matt, Letās say task A referred to task B in a comment. What we are thinking is, in the list of of tasks that referred to B, let users click on X to remove each reference history. But the comment would still remain in task A. Referring to a dependent task in a task name is a cool idea. We shall think about it and get back to you if anything.
Crystal, Jun 14, 2018
I really don't see what that has to do with task dependencies. Task dependency is about getting a notification that when I complete Task A, Quire issues a notification that task B is unblocked and can be completed. An the other way around, when I want to complete task B, Quire notifies me that I first need to complete task A.
(deleted-B5Bn), Dec 10, 2019
Task dependency can be seen from two sides:
- Task A is Blocking task B or
- Task B is waiting on Task A
In Clickup you see these dependencies from both sides, in Task A and Task B. Nice solution, also for Quire.
(deleted-B5Bn), Dec 10, 2019
Hi Matt, You are welcome. š And thank you for the suggestion and lovely example. What we are considering is to show tasks that have āreferred toā a certain task in this taskās detail panel. For example, 10 tasks from 5 sandwich projects depend on the task āBake Breadā. Then, when you refer to this task in these 10 tasks (like in a comment saying ādo this after #BakeBreadā), you will see a list of these 5 tasks in āBake Breadā, thus letting you know its weight. Let me know if this would help.
Crystal, Jun 13, 2018
Personally, I see all of those as work arounds. It's too much maintenance and in the end it is tag which you need to watch yourselves and can easily be missed. I would like to have a notification when a task is blocked or gets unblocked by another task. But if it works for you, that's great.
(deleted-B5Bn), Dec 10, 2019