Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Recognize priorities within task #2996

Closed
4 tasks done
NT3R117 opened this issue Jul 31, 2024 · 3 comments
Closed
4 tasks done

Recognize priorities within task #2996

NT3R117 opened this issue Jul 31, 2024 · 3 comments
Labels
duplicate This issue, pull request or discussion already exists scope: parsing markdown See also 'scope: global filter' type: enhancement New feature or request

Comments

@NT3R117
Copy link

NT3R117 commented Jul 31, 2024

⚠️ Please check that this feature request hasn't been suggested before.

  • I searched previous Ideas in Discussions didn't find any similar feature requests.
  • I searched previous Issues didn't find any similar feature requests.
  • I am only requesting a single feature. Multiple changes should be split into individual requests, with links between them.
  • I believe my requested feature will be generally applicable to other users, not just me: it is not uniquely tied to my personal workflow.

🔖 Feature description

I would like to know if it will be possible to add the ability to recognize task priorities within task text using queries, at the moment the priority of a task is not taken in account if the symbol is not at the end of it.

image

Priority in the example :

  • Has been added with prompt window,
  • There is a space before and after the symbol.

✔️ Solution

It will be great if the priorities can be identified using regex (for instance) no matter where it has been placed within the task.

❓ Alternatives

No response

📝 Additional Context

No response

@NT3R117 NT3R117 added the type: enhancement New feature or request label Jul 31, 2024
@claremacrae claremacrae added the scope: parsing markdown See also 'scope: global filter' label Jul 31, 2024
@claremacrae
Copy link
Collaborator

Yes, I'm afraid this is a known limitation of Tasks currently.

Putting any text after Tasks emoji or dataview fields prevents the fields from being read.

It's documented in several places in the user guide, the most detailed being in What do I need to know about the order of items in a task? and the following section.

We are already tracking this ordering limitation in issue #1505. Please do up-vote that with 👍. Thanks.

@claremacrae claremacrae added the duplicate This issue, pull request or discussion already exists label Jul 31, 2024
@NT3R117
Copy link
Author

NT3R117 commented Jul 31, 2024 via email

@claremacrae
Copy link
Collaborator

No worries. There are so many requests it can be hard to find similar ones. Thank you for looking - it's much appreciated.

@claremacrae claremacrae closed this as not planned Won't fix, can't repro, duplicate, stale Jul 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue, pull request or discussion already exists scope: parsing markdown See also 'scope: global filter' type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants