I have created a Azure DevOps hub extension, it retrieves work items and the goal is to then move some of the work item notes over to Project Online Timesheet Notes. But I can't figure out how I can authenticate my calls from the Azure DevOps Extension to be able to call Project Online.
It seems like the
.getAccessToken(...)
call in the sdk gets an access token encrypted with my extension data, but I need some way I can call into Project instead. I looked into MSAL and it seemed like a good option except I then need to register my extension as a SPA and I can't confirm where it will live.
I'm trying to avoid having the user provide user/pass, anyone know another way?
After speaking with Microsoft learned that this is not supported by Project Online. I was specifically trying to connect to the timesheet for Project Online and was told that it is not supported by the code.
Related
When I get a code review from another person, sometimes the code review states the project name and list the files that are contained in the review. More often than not, it just says none. (please see red box in the image below)
Unless the person gives a good title, it can be difficult to know which project I need to review.
When I open the review, all of the files show up and everything works just fine.
Its only the email that seems to be the issue.
Does anyone know how to resolve this?
I can reproduce above issue. It seems that the problem resides in azure devops server.
You can report this problem to microsoft development team. Hope they will look into this issue and provide a fix soon.
Click here to report a problem(Click Report a problem and choose Azure devops or Azure devops server if you are using on-premise server).
I would like to know how to use/move azure boards with activity date to a different organisation project..
If you are referring to moving work items from one organization to another, you can use the Excel to export and import the work items to achieve this .
First, you need to create a query to get work items, then install the Azure DevOps Office Integration Tool in azure devops , in Excel click on the Team button and then New List to get data from Azure DevOps to Excel, and finally publish work items to destination organization.
For detailed steps, please refer to this blog.
In addition, another way is that you could think about using third party extension tool like the Migration Tools for Azure DevOps . You can refer to this similar case.
I am using Azure DevOps Code Search but I am only able to search in the code as it looks now. I would like to search in the code as it looked like 18 months ago.
Some bit of code disappeared at some point and I would like to get it back. But I don't remember which file it was in so I need to search across all files in the repo.
Is it possible?
I am using Azure DevOps (also called VSTS or visualstudio.com).
I have installed the Code Search Extension.
Search code in VSTS / Azure DevOps back in time
Sorry for any inconvenience.
I am afraid the Azure DevOps extension Code Search does not support history search at this moment.
According to the document How To: Use Code Search, which supports following tasks without history:
Search across all of your projects
Find specific types of code
Easily drill down or widen your search
Some other members submitted a related feature request on our main forum for product suggestions:
Azure DevOps extension CodeSearch: Also search in history
You could vote and add your comments for this feedback. When there are enough votes for this feedback, the product team might consider implementing it.
Hope this helps.
Unfortunately this is not possible as of now.
You can upvote the idea created in developer community for the same - https://developercommunity.visualstudio.com/idea/365924/search-filter-commit-messages.html
The request is currently under review. Till then you can follow a couple of suggestions provided in the idea chain:
Use the GitLens extension on VSCode
Use GItk
Hope this helps!
Added many extensions from a marketplace such as Calendar and it is visible under Boards on the left pane. However, how do I sort them when there are many extensions added to my Boards?
Unfortunately, we are not able to change the order of any installed extension or build-in feature with boards under web portal UI.
You could submit a feature request in our official link.
Beside, not all extensions are installed in this specific place(actually only a little), it's based on the developer of the extension. You could check more detail info from here-- Develop a web extension for Azure DevOps Services
Not every extension adds a custom work hub as Calendar does. In fact, I suspect only a few of them do. Other extensions enrich other areas with new functionality. Often only build tasks are brought in.
There's definitely no filter option under the Boards hub. If there are plenty of custom work hubs, you'll have to scroll through those.
On the other hand, the Manage Extensions view has a nice and convenient Filter option:
I'm considering setting up Intranet-level Nuget feed(bunch of teams in my company are supposed to use it).
I've looked briefly through some tutorials + appropriate chapters in Pro Nuget book, however I still do have some question left so far:
How to make windows integrated security working on private feed smoothly and customize access rights for private Nuget feed(for instance, grant everyone to get packages but grant pushing only to several domain users/groups);
How to allow developers to push packages to private feed without having api key?
How to save developers from making such silly mistake as pushing package to public feed? Is that enough to not configure api key for public feed as default?
Has anyone faced with one of these cases?
I did not try this so far, but following those instructions : http://docs.nuget.org/docs/creating-packages/hosting-your-own-nuget-feeds
I would just create a network share on the server hosting the feed, with write access to specific AD group of developers.
This way your repository is public, and only some persons can add packages to it.
Even after, if you have a continuous integration server, you could allow access to the file share (or API key) only to the account building packages. This way packages are published automatically after having passed automated tests.