This would allow tasks run from home screen to have priority over anything in the background. A dynamic starting priority would be huge for other reasons as well. It could default to 7 as currently operating, but be changed as needed.

Goal: WaituntilTime TIME set in context (like implemented WaitUntil) is reached OR Condition is met

The actual implemented WaitUntil waits forever until condition is met. That produces "hanging tasks". It continues to wait even if the task was stopped by STOP task... It also confused me the first time, as I thought the time that can be set is the max. time it waits (even if condition is not met). But it is the cycle time for checking the condition.

It would be very useful for me to have a way how to force s HTTP request to be routed using the WiFi connection. Especially when the system is using mobile data and I join a WiFi network which requires login in captive portal. I have a task which does this, but when i have my cellular data active this request is just sent using the LTE connection.

Alternatively there could be some option to handle Sign-In portals, but that seems to be even more work.

Add background color and text color options to dialogs for a touch of customization, useful if you are creating an app or scenes with specific colors that identify the design.

Any chance to add a variable that can fetch daily screen on time (not from last full charge) would be great.

The default behaviour of notification actions (the buttons on a notification) for most apps is that they do something as well as dismiss that notification.

In tasker you can only assign a single action to a notification action button. For more complex actions you have to point to a task.

It would be great if a checkmark can be added to the notification action to also dismiss the notification when it's clicked. That would make this behavior a lot easier to program in tasker.

When we rename tasks or profiles, the actions which call them are updated automatically.

But if we change a label text, there may have been a GOTO action referencing it. This won't be updated, and then the GOTO is broken because it points to nowhere.

I recently started using tasker and now I am sort off addicted to it. One feature which I would and many others would love is an auto save feature which autosaves the tasks whenever a change occurs. Sometimes I quit unknowingly and lose all of my progress. Thank You  

I'd like to be able to have an optional parameter filled with a variable name and still be able to use it as if it had not been filled at all. For example, the "Default" field of the "Variable Query" action. When left blank, the dialog has nothing filled in, but if I put a variable there, regardless of what the variable contains, the dialog will always have something filled in. The best I can do is have the variable set to just a space, but then it's highlighted and if the user taps the edit field before typing the

Can you please add blur and dim feature to image?

Idea: Make JSONPath syntax available in tasker.

Currently JSON query syntax in tasker does not support the JSONPath standard (currently in proposed status) as described in https://www.rfc-editor.org/rfc/rfc9535.html and https://en.wikipedia.org/wiki/JSONPath

In particular arrays are awkward to deal with, especially for more complicated structures (arrays in objects in arrays... etc.)

It's possible to work around this at the expense of additional tasker actions, or by using Javascript(Let) but it would be preferable if the standard was provided for.

Some examples which don't work well are: %my_var(N)            Nth element of unnamed array. Have to use the rather ugly

Hello,

In tasker app there is no decimal

Please include decimal number in "Task"  variables "Variable add > Value"

1. I can not add decimal number like 0.5 or 0.3 or 0.003, I suggest to inlude three to four zero after points = 0.0001, hence can use it

If I show a scene and check "Continue Task Immediately" it is cumbersome to destroy it manually if the user leaves.

Can we have an Option (e.g. Checkbox) to auto-destroy a scene on dismiss (back button press, home button press, ...) for the "Show Scene" task?

Sometimes, actions do not time out properly and a task could literally end up running indefinitely causing device to heat up. Add an option in task settings to force kill the task after x seconds.

In scenes could you please update checkbox and toggles so that their default value can be variable driven? Currently you can only choose of they are on or off instead of setting the state with a variable.

The command system is incredibly powerful and simple to use, it can be used as a way to simplify various projects and tasks into a single one that takes the command and does stuff based on the command itself.

It is easier than "Run Task" because the syntax is significantly easier. However, the drawback is that if you have one task that triggers a command and another that gets triggered by it, the first one has no way of knowing if the second one finished without problem, as there's no "return variable" option and no way to logically allow it.

I have two smaller proposals:

1. 

it would be useful to add to Stop task possibility of:

- stopping parent task (both anonymous and named) 

- stopping all parent caller tasks

currently it can be done by parsing %caller() variable but it is difficult and not possible to obtain task name for anonymous tasks

2. 

Possibility to set cooldown times on profiles for both active and inactive states (currently is possible for active state only)

These two things can be useful for situations where for example I need profile with state WiFi connected and need to prevent situations where I'm

How about adding option in the Music Play action to choose an internal ringtone from the ringtones/notifications menu of the device? There is the Play Ringtone action but as you know it can do a lot of harm (less funny) when you get loop of audio playing. I would even suggest to remove it completely and adding all the options to the Music Play action but i know you afraid of breaking stuff for users.

I restored the Tasker settings to a second device (same model) I had installed a Custom-ROM on. The backup contained many tasks that need storage access. When one creates such a task manually Tasker requests permission for that access. This does not happen when tasks are restored from a backup. Now each time such a task is triggered by a profile for the first time, Tasker requests storage permission. But the request neither contains the task nor the requested directory. This is very inconvenient and may lead to data loss.

I have two requests:

1. Short term: Show the requesting task

As it is currently available in scenes. Thanks