My manager asked me to create a resource work and project tracker in sharepoint or lightswitch. Is there any default template to do that... Basically I want to add up a team, resource, project, work items, approval flows in it.
Check out the Lightswitch Starter Kits, you could particularly use the Time Tracker kit to see projects, teams, and approval flows in action. Then extend it for your needs.
Related
Currently based on https://github.com/Azure/portaldocs custom Azure Blades can only be developed internally within Microsoft Product Groups, however they are using React Templates to provide a customized view for custom resources. Ibiza Extensions (Codename for the Portal) would be a great extension on top of custom resource providers.
Is there any capability to onboard resources from organizations, which published their service through the marketplace and/or partners after going through the official onboarding process?
I've checked through the https://github.com/Azure/portaldocs documentation to understand the process and details on how to get engaged. The repository however does not intake any issues to ask there.
Currently we don't have any plans around extension development in our roadmap in the near future. In general, we would prioritize against existing backlog, add in roadmap as appropriate and would announce and/or update the related Azure document once any feature request is addressed.
Azure boards MS Team integration. Only showing Issues or Epics, where are my work items?
I added a tab into a Team channel, and I can see Issues, but there is not option for showing the Work Item field?
On the Azure Boards website I see both fields: Issues and Work items.
Here is no Work Item field
This is the website showing both types at once
As I understand, you are not able to see work item field.
If you need to see work item field,
you need to connect to a project and not just a repository.
From the connect to a Project dialog.
Use CTRL-Shift to select your options and then choose Connect.
The new Work Items experience is available when you connect to a Azure Repos Git repository.
For further reading please follow the document.
You need to set up and manage subscriptions for creating and updating work items. You can create subscriptions to monitor work items at any time using the #azure boards subscriptions command.
Please go through the documentation for more info.
wow I can believe after almost a year nobody replied you. You can set it up in the Organization Settings > Boards > Settings then you can see the process selected. e.g Agile, Basic (what you mentioned) Scrum, etc.
I hope helped someone after this.
I have two Projects in one Organization (like in the attached image below).
I would like to see the items from both Projects in the same Azure DevOps Board (dashboard).
Azure DevOps Boards (dashboards) show just the items from the selected Project.
How can I add items (User Stories) from both Projects to the same Azure DevOps Board?
(There is pretty good documentation on https://learn.microsoft.com/en-us/azure/devops/boards/?view=azure-devops but I did not find the answer)
How I can add multiple projects on the same Azure DevOps Board?
Just as we know, Azure DevOps Board is associated with an Iteration Path(Agile). An iteration path only exists within the context of a Team Project. So, Azure DevOps Board boards by their current implementation live only within a Team Project.
As a workaround, you can try to use the extension Delivery Plans, with Delivery Plans, you gain tailor-made views across several teams and their development backlogs—stories, features, or epics. You can use these views to drive alignment across teams by overlaying several backlogs onto your delivery schedule:
Check the document Managing project schedules across teams with Delivery Plans for some more details.
BTW, there is a user voice Single Dashboard for Multiple Projects, which is on the roadmap, you can vote and track the feedback from this ticket.
Hope this helps.
You cannot do that. I think you have to use one team project and several teams. Just create separate teams for each project. Azure DevOps will create an area path for each team. Then each team will use their own backlogs. In the default project team you can select "Include sub areas," and then you will see items for all teams (or projects).
Additional links:
Add a team, move from one default team to several teams
Define area paths and assign to a team
I'm looking at upgrading my current TFS instance and planning to copy and restore databases as per Microsofts Advanced Upgrade which means I am pretty much installing the new product from scratch and restoring the databases then running a migration tool.
I see in the installation notes that you can integrate SharePoint with it as an optional extra. Why would I do this? Is the idea to store project documentation in a SharePoint Document library per project and be able to link to that content rather than as an attachment to the Backlog Items and Bugs in TFS?
I'm having trouble finding any documentation of team workflows with SharePoint and TFS and I suspect that its because no one really does it.
More importantly would SharePoint integration impede future product upgrades or moving to Visual Studio Online?
In my eyes, SharePoint as a TFS portal has become much less desirable due to the improvements in Team Web Access (eg Charting) but it still has some uses.
With the integration enabled, you will see a Documents tab in Team Explorer which will take you to the dedicated SharePoint Portal (created when you create the TFS Team Project) where all your documentation can be stored. Of course without SharePoint integration you can still happily link Work Items to documents in SharePoint, you just don't have a dedicated portal created for you.
If you are using one of the MSF process templates then some useful documents are created for you on SharePoint when you create the Team Project (xlsx reports etc). However, if you are using the much better VS Scrum template then no documents are created even if you have SharePoint integration enabled.
If you are using the Enterprise edition of SharePoint then you get some good dashboards (bugs, code quality etc.) and you can also publish your custom excel reports easily. This functionality requires Excel Services and so is not available in the standard edition (there are some dashboards created but they aren't that useful).
Share information using the project portal
https://msdn.microsoft.com/en-us/library/ms242883.aspx
Your team can use the SharePoint portal to share information in the following ways:
Share data contained in reports or dashboards
Share team progress using predefined or customized dashboards.
Share documents, files, images.
Share team knowledge and processes using the SharePoint wiki.
Reference process guidance for select team project artifacts.
If you want to add a portal to an existing project:
Configure or add a project portal
https://msdn.microsoft.com/en-us/library/ms242865.aspx
I have a calendar on a SharePoint 2010 site and I have created a custom site template based on the standard meeting workspace. I'd like to force users to only be able to use my custom template.
One option is to add Hidden="TRUE" in webtemp.xml for all other meeting workspace templates - this will leave mine as the only option. This, however, works on the farm level and I'd like to keep the templates available for other web applications. If I can do this on a web application or lower level it will do the trick.
Even better solution - if I can make the new event dialogue skip the step altogether and use my template without asking.
Background:
My custom template only contains security customizations, no UI or content changes. I want to impose it as I have requirements for the permissions of the meeting workspaces which are different from the parent site - so inheritance has to be broken. But I can't think of another way to supply default permissions other than by using a site template for the workspace.
Site Settings > Look and Feel > Page Layouts and Site Templates
choose the site templates you want to be used in the site, this can inherit all the way down the site collection or you can start in a subweb.