How can I associate a PR with a work item in a different subscription - azure-devops

My distributed team works in two different subscriptions, lets call them
sub1.visualstudio.com and sub2.visualstudio.com. It's not practical to add them as a team in our company account, as suggested here: Can I link a pull request to a work item in a different VSTS account?
Our repo is in sub1.visualstudio.com, but the other team keeps its work items in sub2.visualstudio.com
How can I associate a work item in sub2.visualstudio.com with my PR's in sub1.visualstudio.com?
Alternatively, Is there any way to mirror work items between two subscriptions with some kind of bot connector or something?

afaik, it is not possible to connect PR from one subscription to a WI in another. The only way to link them would be by adding an external hyperlink.
The are a few options to replicate your workitems. For example, one would be to use a Logic App in Azure which will be triggered automatically on update/create etc... The other way would be to use, for example azure-devops-migration-tools and create a schedule.

Related

How to change the watch setting on multiple repositories?

I joined a team that has 100+ repositories on GitHub and the watch default setting is ON. I just need it on a handful of repositories. Is there any way to change this setting for all repos without using the web UI and changing it one at a time?
Not that I know of.
In that kind of use case, I would create a second account, and monitor only the few repositories I need from said second account.
That way, I don't have to fiddle with the existing settings for the first account.

Closed - Duplicate a customized work item to be rehused for others work items Azure DevOps

Enviroment:
Azure DevOps
Action required:
To duplicated a custom Work Item to be rehused for others that requires that exact same lyout
Detailed description:
For a new Team Project is required a very specific setup, that was not easy to anchieve and needs to be replicated across all the rest of Work Item types like User Stories, Tasks, Fetures and so on and it would consume to much time do it manually (we are system engineer so there is always a better way ;) ) so for that reason is required duplicate the Taylored work item
I am afraid there is not such a feature to duplicate a custom work item tpye in azure devops currently. You may have to manually duplicate the work item types.
You can click here to submit a feature request to microsoft development team. Hope they will consider implementing this feature in the feature sprint.

Ways to provide read only views of subsets of DevOps work items

I use Azure DevOps to track work items and bugs for a project. I'd like to grant certain people external to the project a read-only view of work items that are related to them (eg. tagged Person X), but without having to grant them access to DevOps. I have been toying with the idea of setting up a flow in Power Apps to continuously update a shared excel spreadsheet based on work items in DevOps, but I fear I might be missing easier/better options. How would you provide a limited read-only view of a backlog to externals?
I'd like to grant certain people external to the project a read-only
view of work items that are related to them (eg. tagged Person X), but
without having to grant them access to DevOps.
For this issue , I am afraid that this is unachievable in azure devops. At present, there is no such permission setting in azure devops to restrict external people can only read work items with specified tag.
You could add your request for this feature on our UserVoice site , which is our main forum for product suggestions.After suggest raised, you can vote and add your comments for this feedback. The product team would provide the updates if they view it. Thank you for helping us build a better Azure DevOps.

Is it possible to move project collection between two organizations?

We are currently having a project collection with backlogs, sprints, etc. in an Azure DevOps account. There is another organization with completely different credentials to log in that we'd like to transfer this project collection to the other organization. I could not find any features or approaches to complete this transfer. Is there a way to be able to achieve this goal?
There is no way to migrate a project between organisations. This may become possible in the future, but the feature suggestion is 8 years old and hasn't seen progress, yet.
However, depending on your requirements, you might be able to create your own tools/scripts to "re-create" your project in the new organisation using the REST API.

Is there a way to create an organization dashboard in Azure DevOps?

Our team is currently using DevOps and are very pleased with how everything is working. We've setup Dashboards in each project that tracks work items and sprints and would like to do the same at the Organization Level. Is there a way to create a master overview of multiple projects in an organization?
Unfortunately we cannot create an organization level dashboard, it's not supported.
We can only create the Team Project level dashboards for teams, please see Add and manage dashboards for details.
However there's already a user voice submitted here to suggest the feature and it's in planned, but based on the response seems no plans to store a dashboard on organization overview. So you can vote it up and add your comments on the existing user voice or submit a new one to suggest the feature...
In our VSTS Feature
Timeline(https://learn.microsoft.com/en-us/vsts/release-notes/), you
see a feature called “Dashboards – Create dashboard separate from a
team” under “Reporting”
This feature will allow you to create a Dashboard that has no
association with the team. This means you don’t need to create a team,
to make a Dashboard. You can create any number of these Dashboards and
share them with who you want.
However, Dashboards will still be stored with a Team Project. So to
address your scenario (cross-team-project Dashboard), you’ll just have
to pick a team project to store the dashboard.
We don’t have immediate plans to store a dashboard outside a team
project.
Our team was dealing with the same problem as yours, and we decided to develop our own dashboard solution at the end.
After using it as an internal tool for several months, we recently made it available as a SaaS.
You may check it out on meercode.io for more information.
Your feedback will be greatly appreciated.
Behind the dashboard widgets are queries, and it is possible to execute those queries across multiple projects.
When you open the query editor, there is a checkbox:
"Query across projects" checkbox (imgur)
This way we created a project in Devops that only contains a dashboard that shows all work items in any project, assigned to or followed by the current user.
That and some nifty colored tiles =)