tgrosinger / tq-obsidian Goto Github PK

If you click the chevron to expand a task that does not have a due date, it will error and the plugin crashes.

Uncaught (in promise) TypeError: Cannot read property 'format' of undefined
    at Object.c (eval at <anonymous> (app.js:1), <anonymous>:40544:55)
    at Object.p (eval at <anonymous> (app.js:1), <anonymous>:40747:16)
    at update (eval at <anonymous> (app.js:1), <anonymous>:15296:36)
    at flush (eval at <anonymous> (app.js:1), <anonymous>:15264:13)

When a task line is expanded, include any additional content from the task note.

I would like to use the dataview plugin to create a table of tasks so I can see most of the attributes of the Tq task files. Can can the field name for the task in the tq files be exposed to enable this approach?

Describe the bug
According to the documentation, the following codeblock should create a list of uncompleted tasks due today or which are overdue.

select-day: 2021-06-06
completed:  false
overdue:    true

However, changing only the select-day property to the current date, the block generates a list of all uncompleted tasks, including those without any date.

To Reproduce
Copy and paste the code block into an Obsidian note. Change the date. Go to Preview mode.

Expected behavior
I expected to see a list that only contained overdue or currently due uncompleted dates.

Screenshots
See attached...

Desktop (please complete the following information):

• OS: [Mac OS v11.4]
• Obsidian Version: [e.g. v0.12.11]
• tq Version: [0.4

Additional context
Add any other context about the problem here.

hi tony, i have no idea how to contact you so i'm sticking this here. feel free to delete after reading.

i just want to give you a big heartfelt thank you for your efforts to create a simple task plugin for obsidian. just enough to do what you need without extra fluff. still has extra power and magic to pull things together.

dataview and other plugins seem rad as heck but seem to require more javascript/typescript know how than i have. this made it accessible for me, a non-dev, to use obsidian as a project manager outside of tools that lock my data.

thank you, thank you, thank you!

Adding a due date to a task which currently has none replaces the contents with just the due date.

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Having a single panel for all tasks with the ability to add a new task would be incredibly helpful to my workflow.

Describe the solution you'd like
A clear and concise description of what you want to happen.

There is a UI in your usage gif (see the 42.31 seconds mark). In it, you have a 'create new task' function which pairs well with the one-click 'add panel' functionality which will work well in my workflow.
Will you be releasing the UI sometime in the future?

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

I have created multiple views using the plug-in queries, setup hotkeys and created data view tables. My next step is to play with the url option outlined in the plug-in documentation.

Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.
ability to add custom metadata to tasks

Describe the solution you'd like
ability to add custom metadata to tasks

Describe alternatives you've considered
template for new tq notes?
option to add custom metadata

Additional context
Add any other context or screenshots about the feature request here.

An opposite to select-tags

Checkboxes aren’t rendering properly when themes are applied.

To Reproduce
Steps to reproduce the behavior:

1. Enable plugin and minimal theme (or any other)
2. Run create task command
3. Observe modal

Expected behavior
Expecting to see checkboxes. Instead, see either oversized ones or barely visible ones.

Screenshots

Desktop (please complete the following information):

• OS: MacOS Catalina 10.15.7
• Obsidian Version: v0.12.12
• tq Version: 0.4.0

Additional context
Pretty sure this is because obsidian expects checkboxes to exist in a particular context.

Generally, checkboxes have a class named task-list-item-checkbox and live somewhere in a container that has the class markdown-preview-view. Without those classes the checkbox doesn’t render correctly.

Is your feature request related to a problem? Please describe.
No way to easily see what was completed on a specific day without going through all tasks individually.

Describe the solution you'd like
I'd like to be able to add a block to my daily notes that shows the todo's completed on that day.

Describe alternatives you've considered
Haven't found any way to do this.

Describe the bug

I'm not sure if it is a bug, but...

I have several tasks that repeat on certain week days. Today, after opening a note with code block to display tasks, I found an empty list. I used the query:

completed:  true
overdue:    true
due:			true
no-due:		true
sort:			"score", "due", ""
group:		"due", "completed", ""

I see two repeatable tasks in my task folder, but they do not show up when queried. Then I was thinking about how those tasks are created?

Expected behavior

Repeatable tasks are created automatically, even past-due tasks, as you may not open obsidian each day.

Desktop (please complete the following information):

• OS: Win 10
• Obsidian Version: 12.10
• tq Version: [e.g. 0.4.0] (Settings → Third-party plugin → Scroll to tq)

Describe the bug
Using Obsidian Git to sync notes breaks tq functionality. Tasks show up on queries, however, the tasks are listed as having no due date or (tags, i think ?). This therefore breaks filtered queries by making everything show up.

Only until editing a note and resaving it (adding a space) is the task "fixed" and is shown to have a due date.

To Reproduce
Steps to reproduce the behavior:

1. Have tq and Obsidian Git
2. Have tasks dated on several different days
3. import the vault into a new device
4. restart obsidian (just to refresh themes and such)

Expected behavior
Expected behavior is to have tq recognize due dates rather than me having to "touch" the file for tq to update it.

Screenshots

Desktop (please complete the following information):

• OS: MacOS & Windows
• Obsidian Version: 0.12.15
• tq Version: 0.5.1

Additional context
great work so far ! love the plugin.

i have mac os, and i would like to add a time to the task and have it notify me when it is due, with a button to complete if it's possible, thank you.

Is your feature request related to a problem? Please describe.
Not a problem so much as a current limitation: you have to put all your tasks in a single folder.

Describe the solution you'd like
I'd like to store tasks anywhere in my vault, and then have the option to organize them by tag. This would enable me to have tasks that live in specific project folders.

Describe alternatives you've considered
Love the concept of this plugin, but currently working on a temp solution using Dataview, since it allows sourcing by folder, tag, and even [[link]].

Is your feature request related to a problem? Please describe.

When I downloaded the plugin a folder named "tasks" was automatically created under the default vault. I tried placing the folder to a custom location in the vault but then the plugin stopped working.

Describe the solution you'd like
It would be nice if one could choose to place that folder anywhere in the vault. For example: "Notes/Daily/Tasks".

Thank you for this plugin.

Currently, when we query for the tasks in a obsidian note, only the description is displayed in the UX. It will be useful if we can display additional fields like due dates in UX.

If I want to add multiple tags in the dialogue, I can, but only the first triggers the autocomplete function

Is your feature request related to a problem? Please describe.
Obsidian's nested tags create meaningful hierarchies. It would be helpful to be able to create higher-level views in tq. For example, I like being able to view tasks related to "#PROJECT/A." I like being able to view tasks related to "#PROJECT/B." But for weekly and monthly planning and review, it would be important to view tasks related to #Project and see tasks related to both A and B. Of course, I can add multiple tags, but the process would become burdensome quite quickly (I have 47 waiting or active projects in my portfolio right now).

Describe the solution you'd like
Enable tq to use nested tags hierarchically.

Describe alternatives you've considered
The only alternatives I've considered would wreak havoc on tags (e.g. tagging all projects with "#PROJECTS" as well as their specific project tag, because this would have to be replicated for all other categories of hierarchical tags as well).

Additional context
Add any other context or screenshots about the feature request here.

I think a small visual indicator on the side of the row would be sufficient. Similar to what is used by AmpleNote

Describe the bug
This is what I get in the console when I try to turn the plugin on:
Plugin failure: tq-obsidian Error: ENOENT: no such file or directory, open '...\Obsidian\brainforest\.obsidian\plugins\tq-obsidian-0.0.1\main.js'

To Reproduce
/

Expected behavior
/

Screenshots
/

Desktop (please complete the following information):

• OS: Windows
• Obsidian Version: v0.12.5
• tq Version: 0.0.1

Additional context
/
/

Is your feature request related to a problem? Please describe.
Hi Tony. Following development here with excitement. My current challenge implementing tq is that I organize and differentiate projects by folder, not tag. Thus, I don't know how I might be able to build a view of tasks that are related to specific projects.

Describe the solution you'd like
Are you considering adding a "select-folder" property in the future?

Describe alternatives you've considered
Without a folder-based property, I would have to create a tag for each project folder just to achieve this. Not impossible, but unwieldy.

Additional context
I really, really prefer the file-based task approach (as opposed to a block-based task) and hope that you are able to continue with your work! Thanks!

Is your feature request related to a problem? Please describe.
Not really a problem, but I like to give some tasks a "start on" date in addition to a due date, when tasks aren't relevant until after a certain date.

To allow for this, as well as other specific needs, it might be nice to allow for arbitrary custom properties.

Describe the solution you'd like
It would be great to be able to enter arbitrary custom properties in the task note frontmatter, and then query those properties from a tq code block.

Describe the bug
The completed property does not filter on 'true" value

To Reproduce
Steps to reproduce the behavior:

1. Edit a note and...
   a. Create simple tq custom block with "completed: true"
   b. Create simple tq custom block with "completed: false"
   c. Create simple tq custom block with "completed: "
2. Preview note...

Expected behavior
Case 1 ("completed: true") - Fails
EB (expected behavior) - List of completed tasks
AB (actual behavior) - List of all tasks

Case 2 ("completed: false") - Succeeds
EB - List of incomplete tasks
AB - List of incomplete tasks

Case 3 ("completed: ") - Default (per documentation) fails
EB (expected behavior) - List of complete tasks
AB (actual behavior) - List of incomplete tasks

Screenshots

Desktop (please complete the following information):

• OS: [Mac OS v11.4]
• Obsidian Version: [e.g. v0.12.10]
• tq Version: [0.2.0]

Additional context
I think this worked in an earlier version.

Describe the bug

Repeatable tasks aren't shown in the result list of a select-week query if they were completed in this week.

To Reproduce
Steps to reproduce the behavior:

1. Create a repeatable task which is due this week.
2. The task shows in the result list.
3. Complete the task.
4. The task doesn't show as completed in the result list. It simply isn't there.

Expected behavior
I expect that if one of the repeatable task's completed dates lies in the week of a select-week query, this task is shown as completed in the result list.

Desktop (please complete the following information):

• OS: Ubuntu Linux 21.04
• Obsidian Version: v0.12.12
• tq Version: 0.4.0

Additional context
My repeatable task:

---
due: '2021-10-27'
repeat: every 2 months on the last Wednesday
completed:
  - '2021-08-25'
---

- [ ] do this and that...

My query:

```tq
select-week: 2021-08-23

Never mind. I figured it out!

I second the request for natural language processing

Is your feature request related to a problem? Please describe.
I like to keep my task list on my daily note, filtered by those due that day and priority levels (e.g. P1, P2,...PN). Currently, with tq, the only way I can see to filter for tasks due that day is to manually input the current date each day in the filter query.

Describe the solution you'd like
Being able to describe dates in the query using natural language, such as select-day: today, would mean that I could just put that generic query in my daily notes template and not have to adjust the query each day.

Describe alternatives you've considered
I've considered having a single page that represents the overall status of my task list, demarcated by days similar to the examples in the README. The reason I prefer not to do this is because I like to keep my tasks relatively isolated from each other so that I can just focus on the tasks at hand and not feel overwhelmed by those due before or after. Think of it as separation of concerns.

Additional context
Here is my current workflow with an alternative task management system. tq has, in my opinion, a much cleaner UI and I love certain features like the use of the calendar for date selection.

Describe the bug
A clear and concise description of what the bug is.
The custom blocks are just rendering as a code block where the query is shows as code. For example this:

looks like the following in viewing mode:

To Reproduce
Steps to reproduce the behavior:

1. Create any custom block
2. view it in viewing mode

Expected behavior
A clear and concise description of what you expected to happen.
Expected behavior is to see the tasks that the query produces in viewing mode

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Ubuntu
• Obsidian Version: v0.12.8
• tq Version: 0.0.2

Additional context
Add any other context about the problem here.

If I specify today date select-day: 2021-07-26, why I see completed yesterday tasks? I want to see tasks I done today only. How to do that?

Is your feature request related to a problem? Please describe.
It's not really a problem.

Describe the solution you'd like
I like to group tasks by having a master task item that composes of multiple sub tasks. Currently, this does not seem supported in the plugin, as the query UI does not show the nested tasks.

In the task itself, you can already see what I'd like it to look like.

Describe alternatives you've considered
This is solvable by just using one 'real' task per sub item and selecting them in a separate query. This allows for more detailed metadata per task as well, which is lost in the example I've pulled together.

Additional context
Downside of the approach I show above is that only the parent task has the tracking metadata. It might be cool to link a parent task to child tasks so you keep all the tracking features while also be able to (maybe automatically) check the parent task when all child tasks are done.

Let me know if you need more context or explanation.

Currently there is no way to show a task before it is due unless you show all tasks.

It would be nice to be able to indicate that you want to see a task X days before it is due, or show it starting on a certain date.

More thought will be necessary about how this fits in with select-date or select-week.

Is it possible to make, along with select-day and select-week, also a select-month field?

Is your feature request related to a problem? Please describe.
When I check an item off, I thought that the task would record the date it was checked off. If this is a feature already then I'm not sure how to enable it. Knowing when I did something is sometimes important information in the future.

Describe the solution you'd like
Checking an item as done adds the current date(time?) to the note, either in the body or the metadata. I think metadata would make more sense of course. Or, using a command to mark task as complete does both.

Describe alternatives you've considered
I could write in the date/metadata myself before checking it off but that feels unnecessary.

Additional context
Add any other context or screenshots about the feature request here.

Is your feature request related to a problem? Please describe.
I know I have made a number of feature suggestions in the past 72 hours, and if I knew how to write code, I would contribute :) I also know and respect that you are focused on enhancements that address your workflows. But I think this could be a very useful suggestion.

A lot of my tasks in Obsidian relate to a note I am working on. It would be incredibly helpful if I could create fast, fluid associations between tasks and notes. I think this could be accomplished if the task description could default to the name of the active pane (instead of random phrases like "Weed the garden"). If used, this would create an "unlinked mention" on both the original note and the newly created task!

Describe the solution you'd like
Could users have an option in settings to prefill the description field with the name of the active pane? You might also include a second option to place that name within double brackets to create true Obisidian links, but I'm not sure if that is necessary.

Example:
I'm working on a note called "Annoy Tony with feature requests" (which contains a running list of feature requests) and I trigger the create task dialogue. Because I have checked the settings option to prefill the description field with the name of the active pane, the task description is prefilled with "Annoy Tony with feature requests." The task is created as - [ ] Annoy Tony with feature requests and I can quickly jump to the original note via unlinked mentions in the outgoing link panel.

Aside from the frivolous example above, this would have value for many use cases. For instance, if I had a literature note, I might want to create tasks to outline each chapter. The task name would default to the active note's title, and I could just prepend it with "Read CH1 of" to get a meaningful, linked task.

Describe alternatives you've considered
I'm doing a lot of cutting and pasting to achieve this now.

Additional context
If there were a technical difficulty with this request, a viable alternative would be simply to include a checkbox in the create task dialogue that insert a link to the note in the active pane.

Is your feature request related to a problem? Please describe.
If I want to see tasks from today and yesterday, I have to manually edit my query each day.

Describe the solution you'd like
I would love to be able to use relative dates (like "select-day: yesterday") so that I can embed a query in a template that will always show me today's tasks and yesterday's tasks, without me having to manually edit the select-day property to reflect yesterday's actual date.

Describe alternatives you've considered
I played around with ways to accomplish this, but haven't been successful. If such a mechanism already exists, please pardon the noise!

Hi,

I've created a Zapier recipe to create a task note from my browser that captures the active web page title and url. Everything is working fine, but I am facing one "inconvenience" and I'm not sure if it can be addressed.

It appears that if a task is created manually in Obsidian (or via my Zap) -- that is, not using the TQ ribbon interface or palette commands -- the plugin won't "register" the task until either the note content changes (by adding a character) or until the plugin reloads when Obsidian is closed and relaunched.

Since I'm not a coder, I can't even begin to imagine how the plugin works, but it does seem to monitor a task note's last modified date value. Is there an easy way to monitor for the "unexpected arrival" of a new note in the designated task folder?

Thanks,
Jack

Describe the bug
I have a repeating task due on the last day of the month. If I complete the task early (like I did today), the task is marked as completely but the next due date remains the same. For instance, a repeating task due on 7/31 but completed on 7/30 is reset to 7/31 rather than 8/31.

To Reproduce
Create a repeating task for the last day of each month
Complete the task prior to the last day of the month

Expected behavior
I expected the task's next due date to be set to the following month.

Screenshots
n/a

Additional context
A bug or a feature :) ?

Describe the solution you'd like
Have an option to name tasks by date and time of creation or have the tasks created in the same note with the date of the day as the title.

Additional context
I would like to be able to use the Obsidian Tracker plugin to keep track of my completed tasks but having the tasks created as random names is not possible.

Is your feature request related to a problem? Please describe.
I like to keep a running list of things I completed that day, but also, yesterday I "completed" something, to realize that it's not actually completed and I want to "uncheck" it.

Describe the solution you'd like
So it'd be nice to be able to query for "recently completed tasks" to find the task and untick it, and also have a query for "tasks completed today" in my daily template.

Describe alternatives you've considered
Currently I can do a full vault search for the plaintext of the task, find it, then untick it.

I'm currently thinking moving to a new task management system in Obsidian, and I was wondering when this plugin might be coming out since I don't want to need to swap again later on.

Also, do you mind sharing some of the functionalities that the plugin might have?
I saw a lot of interesting things in the commits.