Does Team Foundation Service have a built in Wiki like GitHub does?
If not is there one that can be easily integrated?
No it does not, you could try using CodePlex instead. This has the option to store your source code using TFVC and use Team Foundation features such as work items and queries, but also allows you to have "documentation", which is in a wiki style.
Team Foundation Service is Cloud Hosted TF. CodePlex is Microsoft's open source platform.
Brian Harry as also stated there are plans to align CodePlex and TF Service most closely.
And, as I alluded to earlier, we’ll be working to align CodePlex and
Team Foundation Service into a single, scalable offering.
Visual Studio Team Services now includes a wiki, though it's currently in preview mode. To enable it, select "Preview Features" in the profile menu and set the wiki to on.
Detailed instructions are at https://www.visualstudio.com/en-us/docs/collaborate/add-edit-wiki
Related
I have an existing project that uses project boards on GitHub. I want to move all issues (open and closed) to projects (beta) on GitHub. Is there a way to do that automatically? Right now, I only know how to add issues manually to projects (beta).
As far as I know, there is currently no official guide on how to migrate to GitHub Projects (beta). You might want to follow this discussion on the topic: https://github.com/github/feedback/discussions/6141
However, I created a tutorial on how to migrate from the legacy project boards to the new projects (beta) myself: https://github.com/galargh/projects-migration#how-to-migrate-from-github-projects-to-github-projects-beta
It describes how to migrate cards (including column names) by either running a GitHub Actions workflow or a bash script.
Unfortunately, it does require some manual steps because projects (beta) API is not complete yet - the project itself and the Status field options have to be created manually to be precise.
After the migration, I'm also heavily using this action I created https://github.com/protocol/github-api-action-library/tree/master/add-project-items-by-content-query. I use it to periodically populate my projects based on content search queries (e.g. I automated adding all the issues that mention me - https://github.com/galargh/.github/blob/684c316/.github/workflows/add-project-items.yml).
I implemented python script that helps you migrate your project (similar to #galargh's solution) which uses the GraphQL api for the old projects too (might be more future proof) and also allows you to map column names and migrate PRs.
https://github.com/doidor/gh-projects-migration
You can now do this by enabling the Project migration feature in feature preview
Once you enable it you should see a Start migration button when you go to your Classic (not beta) Project Board
Here are the official docs on how to do it
We are using TFS 2015 On Premise, not in the cloud and I am trying to give access to Stakeholders so they can access the wiki. However, as a stakeholder I keep getting this error:
TF400409: You do not have licensing rights to access this feature: Code
After researching the error it seems to be related to the fact that Stakeholders do not have access to view Code Wikis as shown here. That link is for Azure DevOps and I am not sure if it applies to my case but I cannot find anything else so my assumption is it does apply. Even links within our TFS site, takes us to Azure DevOps for help and thus my assumption is it applies to us as well.
Here is a screenshot from the aforementioned link:
Question
What is the difference between Code Wikis and Project Wikis? It seems I need Project Wikis but how do I create a Project Wiki?
Thanks in advance!
Code Wiki are not available on TFS server 2015. You need to use version TFS 2018 or above for this.
Project Wiki
Every team project can have a wiki. Use the wiki to share information
with your team to understand and contribute to your project.
Each team project wiki is powered by a Git repository in the back-end.
When you create a team project, a Wiki Git repo is not created by
default. Provision a Git repository to store your wiki Markdown files,
or publish existing Markdown files from a Git repository to a wiki.
In the project page, you could directly choose to create project wiki.
Code Wiki
Content that you already maintain in a Git repository can be published to a wiki. For example, this could be content written to
support a software development kit (SDK), product documentation, or
README file. You can publish multiple wikis within a single team
project.
More details about the difference of them, kindly refer our official doc here:
Provisioned wikis vs. published code as a wiki
As how to use them in Azure DevOps/TFS, you could also take a look at this step by step tutorial -- Collaborating using Azure DevOps Wiki
As the title implies: is it possible to import a whole project from Azure Devops (TFS) into MS-project?
I am missing the "Team" tab in ms-project.
Is it possible to import a whole project from Azure Devops (TFS) into
MS-project?
Of course yes. In fact, call it import is not accurate. It's work logic is connect the MS project with TFS, then get\access the whole WIT from the TFS project.
As you said, you haven't seen the "Team" tab in MS project, firstly, you should ensure that the Visual Studio version you installed does match 2010 or later. If the version match and still could not see the tab Team, you should follow the below steps to install the Team Foundation Server Standalone Office Integration.
Go File menu, choose Options.
Choose Add-ins and from the Manage picklist, choose COM
Add-ins, and then choose Go.
Ensure that the Team Foundation Add-in checkbox has checked.
Due to this official doc for more detailed steps: Enable the Team Foundation Add-in.
vsts online introduces wiki feature in its latest additions.
Are there any diagramming tool available as a plugin for creating wiki in the newly introduced wiki tool in vsts online?
Based on the wiki extension overview, it will be available.
Built with extensibility in mind
Want to see diagrams, mind maps and more in your wikis?
With the extensibility model we enable integrations with existing
tools to really make your wiki pages come alive.
On the other hand, you can clone it to local and modify, then push to server.
Add and edit pages in your team project wiki
I see this is an old question but there are updates. Azure DevOps Wiki (Services & Server) now supports limited Mermaid diagrams; just Sequence diagrams, Gantt charts, and Flowcharts.
Sadly Azure DevOps Wiki is stuck at an older Mermaid version, making it troublesome to use as the newer, documented Mermaid syntax often does not work.
I'm in process of migrating my open source project from VS Team Services to GitHub (in hope of having actual contributors at least).
Migrating git repository was easy, but now I have a problem of migrating issues.
I don't know how to migrate issues.
I really like Team Services board. Can I get something like this in Github?
For Question 1, there isn't any tool or simple way to migrate the VSTS issues to GitHub as I know since the issues in VSTS are work items that use a totally different template with GitHub. If you have large amount of issues need to be migrated, you may create an application and use VSTS Rest API and GitHub API to do this.
For Question 2, GitHub does not provide Kankan board feature by default but you can get it from some other service. For example: waffle.io