Idea for a Tasker action: sync system account(s), either

• all accounts or
• all accounts of a specific account type or
• a specific account (by name and type).

Use cases (examples):

• sync emails on certain occasions,
• sync DAVx⁵ accounts on certain occasions.

The action would have to

1. enumerate affected accounts and then
2. call ContentResolver.requestSync for each account.

It nice to tasker can export to apk, but when you open apk as zip, it will show data xml is not encrypted, so someone can steal your hard work.

So could be nice to added Encryption at xml task on tasker kid, so someone will not kang it or modify it and then replace your name to their name.

When selecting applications, it is difficult to see such a thin line around the selected application. 

I would like to see Tasker recognize specific angles.  I have a stand that holds my phone on its side and tilted back just a bit.  Having tasker recognize that specific orientation would be nice. 

Right now gd download only downloads files in a folder, plz guve option to download all subfolders and files. 

Array set and push actions "Value" text field does not expand like it does in

variable set actions. Sometimes you need to set a length string and the scrolling thing gets hard to see and edit

The first line of the anchor text should be displayed as the Anchor Action's Label Text inside the Task List so that we know what the anchor is for. Anchors are mostly used for comments and goto statements, and their text should be shown so that the code makes sense more easily, otherwise anchors have to be opened to see what they are for. For people who dont want the text shown could maybe write the text starting from the second line or maybe an option can be added in tasker settings to show or hide it.

Currently the only way to assign a category is to manually type it in. This becomes tedious and error prone when several Notify actions share the same category.

One solution would be to add a 'magnifying glass', which would allow selection of a previously defined category. Would this be possible?

Would it also be possible to add a method to delete categories which are no longer being used?

A simple request. Just as you can create a task without assigning it to a profile, please can we create a profile without being forced to assign a task to it. Yes, I know the profile won't 'do' anything as there is no task, but sometimes having it there is a handy placeholder and provides structure when developing a project.

autonotification is able to block by title or text, but sometimes it would be useful to block by subtext (marked with red box). this way the spotify notification wouldn't pop up on all devices with the same account, but only on the one you are listening on.

It would be nice to have an option in WiFi Near to check if there's a known WiFi available. With this it would be possible to do profiles like:

On event 'Display on' AND WiFi Near (known WiFi) => Turn on WiFi

When complexity increases, meaning when a lot of sensors are included and they all talk to each other to reach certain outcomes, then as to what is going on when it operates there is little to no feedback as to what is needed, in order to understand what is going on.

So with such, there's little to no help, for instance, from RunLog. The best I know is to add voice feedback all over the place to try to make sense of the flows, but I figured it would be great to dramatically improve Tasker with greatly helpful feedback system,

Just like in the log where the user can select Profiles, Tasks and/or Actions; it would be great to have the same selection buttons in Search. The use case would be a more granular search for cases when you know the Task name or that the variable is used in a Profile without having to scroll through all of the actions which use the variable.

Cell Near have the option to ignore certain towers, I don't see why WiFi Near can't have the same option for Mac Addresses(or even for SSIDs, but Mac is more useful to me)

A new option in Test Scene preferably called Elements that'll return the names of all the Elements in that scene.

I'd like to suggest arrayed native/global vars. A user started a forum thread about date/time particulars. It seems to me that a hidden array is the perfectsolution, not just here but elsewhere. Example: DATE returns m-d-yy. Why couldn't DATE(1:4) return numbered year, month, day-of-month, and day-of-week? Same goes for TIME (i.e. hr, min, sec) but perhaps also encompassing TIMES and TIMEMS. Similarly, why not WIFI for the state, WIFI(1) for connection data, and WIFI(2) for scan data. DAYM, DAYW, TIMES, TIMEMS, and WIFII shouldn be delisted rather than deleted so that existing tasks will continue to function  I think this

There are 3 options in setting quick settings action:

Active

Inactive

Disabled

Please add an option named "Toggle" so that there wouldn't be a need to define a wrapping variable to toggle a quick setting. It could be toggled when the option is set and the value of it being turned on or off could be accessible through an output variable. 

This makes tasker a bit easier for newbies. 

There should be an option to change the text size of shell actions and also an option to disable word wrap. Writing multi-line scripts in shell actions is a mess with word wrap enabled and really hard to understand what is going on.

There should be a variable that can be set in place of the root toggle so that commands that are created and run dynamically can automatically set if root will be required or not. Moreover if projects are being shared with other people, some people might not need or want to run shell commands as root. This would make it easier to create those projects with like a global variable maybe. If the value is "1", then run with root, otherwise don't run with root.

Traditional app state contexts work but are static: the only way to change the apps included is by opening Tasker's UI. The App changed event allows specification of included apps using a variable, but this is only an event, not a state.

I would like a combination of the two: an app STATE context which activates only when the app name/package/whatever matches a text field where a variable may be used.