In VSTS Task Groups is it possible to parameterise a checkbox - azure-devops

One of the tasks in my Task Group has a checkbox. Is it possible to set it as a parameter?

For now, the feature is not available. But it's already added in our backlog.
And you can also refer the user voice Allow Task Group parameters to be optional for the feature suggestion.

Related

style taskboard cards using their parent properties

in my sprint taskboard i want to style my tasks based on their parent PBI/bug priority and not having to set a priority for each task. is it possible?
As of this time, however, there isn't a built-in feature to set fields or styles of work items based on their parent fields or styles. Here is a feature request.
If you don't mind extra work, you can get and update fields of the work items through Rest API, and use automation tools such as Power Automate to let the script to run automatically when the a work item is created.

Alfresco workflow create user task dinamically

I have a custom workflow in Alfresco 5.2 community. I have a parallel user task assigned to a activiti:collection="mywf_reviewersAssignees", and that variable is chosen at the beginning of the workflow. All works fine.
Now, under some circumstances, while the reviewers are completing their task, I need to add another user to that collection, so that another user task is created.
I have managed to handle the "when" correctly, but I do not know how to create/add a user task.
In other words I need to "reassign" the task, extending the default Alfresco behavior. Instead of changing the task owner I need to close the previous user task and create a new one to the new user.
Is this possibile?, thanks
EDIT
I've read this link (How to assign Workflow to the new user of the group?) which suggest to use the candidateUsers variable, but I need all of the users complete their work, I can't have them as candidate and let only one to do their work
A similar question is asked here Create User Multi Instance Task Programatically, but unfortunately none answered

Azure DevOps show/hide fields depending on conditions

Is is possible to make a custom rule in Azure DevOps that either shows or hides a field in a work item depending on a condition?
For example:
Condition 1: When a work item is created
Action 1: Hide field X
Condition 2: When work item state changes from Active to Resolved
Action 2: Show field X
I hope someone can help :-)
For Azure DevOps, we can only Create and manage inherited processes to customize the fields/rules.
To hide fields/groups, for some of the existing fields/groups (default fields/groups) we can directly hide them from the layout. For customized fields we can only remove them from the layout.
What you need, there is no such build-in option to achieve.
You could submit a user voice here: Azure DevOps Feature Request

Is it possible to have a "Select All" option for a pickList input in AzureDevOps task?

In a custom Azure DevOps release task, for an input of type pickList, is it possible to have a Select All option?Is there a property to enable that inside task.json?
According to your description, seems you want a picklist in your task such as below:
Unfortunately, it's not supported for a multiple select picklist (include select all) right now.
Kindly refer our official task samples here.
You could also file a feature request. Our PM will regularly review any suggestions.

Add or modify workflow Reasons in Devops Azure Workitems

Presently I am using Devops Azure (Cloud).
For Work items is there a way to add and modify workflow Reasons.
State and Reason change
I am looking to add some custom reasons in the work item for each State.
Is there a way to change these. From the help, its mentioned, "You can add and remove workflow States. However, you can't add or modify workflow Reasons.". Any pointers to do this.
I am looking to add some custom reasons in the work item for each State.
I am afraid there is no such way to add some custom reasons in the work item for each State.
Although we can use custom fields and custom rules, it can only achieve one state for one reason.
That because Azure devops not allowed to have multiple rules with the same action type using the same conditions:
And on the other hand, we also could not add a list as value of Picklist items:
So, I do not believe we could add some custom reasonS in the work item for each State at this moment.
You could add your request for adding a list as value of Picklist items on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
Hope this helps.
There is no any news here. As workaround, you can:
Add a new custom field with a pick list with reasons and mark it as required. Add a picklist.
Use rules to set default values into your new field for each state transitions. Add a rule to a work item type.