I have User A & User B. User B will take over all assigned to work from user A.
Is it possible to migrate all work items, & mentions in pull reques etc from user A to user B?
To migrate all work items from user A to B, you could achieve this by using Boards -> Query.
For migration mentions in Pull Request, currently there is no build-in feature to migrate this.
Run a new query to list all the work items assigned to user A
Choose all the work items and "Right" click to assign to user B.
Then "Save Items"
Related
I want to prevent users from organization to create more than 5 work items in boards in each project. Also want to set a rule as more than 5 tickets if any users wants to create according to business need, we should enable the count.
Is there a way to do this??
Azure DevOps does not support such restrictions. In this case, you have to create your custom application via Rest Api, that rejects or deletes restricted work items:
Search work item: Query By Wiql, use [System.CreatedBy] field in your query
Get work item details (if you need to check some additional fields): Get Work Item
Update state (Update) or remove (Delete) restricted work items.
I have 2 private projects in my Azure DevOps Organization, say Project A and Project B. I need to mention a User in Project B from a work item in Project A. I'm able to do it. But the mentioned user is not able to view the Work Item as he don't have access. Any Solution or Work Around to achieve this?
Giving Reader Access permissions will solve the problem of user being able to view the work item.
If you haven't already given reader access to the user, try giving it and see if that helps.
See the below Image for reference :
Click on Project Settings -> Permissions -> Readers -> Click on Add -> and add that user.
Currently we cannot set permissions for a single work item. If you would like that feature, please use the below link and create a request for this feature: https://developercommunity.visualstudio.com/content/idea/post.html?space=21. This link is directly monitored by the product team and they will look into this request and share their views on the same. If lot of users request for the same feature, they will add this item to backlog to implement in the future sprints.
As a DevOps administrator I want to give restricted access to the backlog of our project to a user.
I want to limit his access. Meaning that the user can only see Work Items he has created in the backlog, nothing else.
Is their a way of doing this?
the user can only see Work Items he has created in the backlog,
nothing else
I am afraid that this feature you want is not feasible.Boards is visible to all members of your organization.
You can only set the member to Project Readers at most, so that members only have read permissions but no modified permissions.
You can set the Assign to filter condition in the Filter of the backlogs to see the work items assigned to a specific person, but it can't prevent the user from viewing the work items assigned to others. In addition, there is no filter condition to see who created the work items.
I am working on some simple queries for Visual Studio Team Services. Is there a way to change the query result based on which user views it?
I know about the #Me operator but for this specific case I want to look for unassigned work items and filter them by current user.
There are 3 backlogs, and user A,B and C. User A is responsible to assign tasks for backlog1, user B for backlog2. I want to have a single dashboard with a query showing the unassigned task. So if user A opens the dashboard it should show all unassigned tasks for backlog1 and for user B all tasks from backlog2.
Microsoft has recently added the #Me token to all fields related to users.
This enables creating queries for the observing user - and in extension - personalised queries on the dashboard.
Additional info and the related docs can be found here
I need to create a multilevel Approval Workflow for following scenario:
Workflow starts once item is created employee (Say in a ProductList) for certain Amount.
Manager Approves the workflow.
If Amount is < $5000, email goes to Employee as approved.
If Amount is > $5000, further approval is required. Item goes for further approval to VP and then CEO.
I am getting many examples on workflow, most of the examples are sending just an email based on condition. I need sending for further approval based on condition.
Create a list with the following columns
a. Product Name (Text box)
b. Price(Text box)
c. Mgr approval (choice)
d. Final approval(Choice)
Hide column c & d using JavaScript when user enter the value
a Create a workflow in item created for sending mail to manager
Show the column c using JavaScript or the manager
Create another workflow for send mail to final approval on item edited event after checking following conditions
a. Amount >5000
b. Mgrapproval (c) status is approved
Show the column d using JavaScript for the final approval
You can use simple JavaScript if the mgrapprover and final approver does not change. If these values are dynamic it is better to create a webpart for generating JavaScript by checking the login user group.
I would do the following:
Create a list with your approval items in it
Create an approval request as you have done
Check whether the amount >= 5000
If it is ask for approval from the VP and CEO (follow the same steps as you do for step 1 but this time using VP and CEO prefixes for your variables and collection tasks).
If possible, I'd also reference external lists for the amount to check at, and for the VP and CEO names - so that you dont have to redeploy the workflows when the amount changes or the VP/CEO change.
Theres a good write up of a similar multiple approval SP workflow scenario here
As an Aside, you might not want to send the emails with the task url, I'd suggest coding the actual edit page urls into the email so that users (i.e. Managers, VP and CEO) dont have to view the task, then click edit item, then approve, by viewing the Edit screen you can get the url and input your Workflow TaskItemID into the url directly which will give the end user a better overall experience. Only one button click to approve/reject instead of multiple clicks to just get to the screen.
I did this kind of thing by having a workflow like yours on the first list and when a certain condition is fullfilled(like >5000$), I move the item in another list where another workflow process it for approval like you need to. It may seem like your multiplicating workflow, but I usually prefer to have more pretty simple workflow than one workflow that does a lot of things.