I work in a large organisation which has many VSTS online projects.
We want to create a custom VSTS online extension and only enable it for selected projects.
I would like to create a Hub extension to make use of the full screen.
The only way I can think of is by creating it as a Dashboard Widget, but this restricts me to a small ui.
No, there isn’t the feature to restrict projects for VSTS extension. I submit a user voice here: VSTS extension project restrict.
The workaround is that you can get current team project by using VSS.getWebContext().project, then just display content for corresponding projects. (Note: Can’t set projects dynamically)
Related
My company is looking to streamline User Story documentation in DevOps's Agile workflow. Is there a way to use markdown formatting in Description / Acceptance Criteria fields in DevOps? It is far more flexible and powerful than the WYSIWYG editor available in DevOps.
You may have known that in Azure Devops, we haven't directly provide such feature in WIT. So, to achieve what you want, just consider to develop an extension.
For VSTS, there has an existing one Markdown. But I saw you tagged this question with a azure-devops-server-2019 tag. If your server type is TFS, please check this extension source code, and then made some customized changes into it to let it available for your server.
See how to develop extension for TFS work item.
The working logic of this extension is adding a custom control which expand Markdown edit into work item layout.
Since what you are using is Azure Devops server 2019, below operation and its action logic also suitable for you.
With more details, in your requirement, you want the fields Description / Acceptance Criteria can support to use Markdown. This extension would let you add a custom control to User story.
Step1: In its custom control, choosing Markdown as control type which can let this field control under Markdown.
Step2: Choose which field you want to show Markdown editor for, here is Description
Step3: Choosing corresponding layout location, store it in to a new group.
Step4: You should not want there has two same editors on the work item form. So, hiding the default one:
After the above steps, now, the Description fields can support Markdown language.
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:
Management would like to migrate all teams using Azure DevOps (VSTS) to a single project to make reporting and work roll-ups easier. if this is done can the individual teams still utilize templates customized to their specific needs or would they need to use the default template for the project.
Thanks
We are being asked to migrate to a "standard" company project but don't know if we will be able to have customization for our process
No. One team project has one process template. You can customize that process template however you wish, of course.
What you could do is create an inherited process in order to make your customizations, and change every Team Project to that Process.
You have to take into account that the customizations you have made to your Team Project could be affected when you change to a inherited process.
Test carefully with some test Team Projects before.
I would like to view all open pull requests across all of the projects under my VSTS account. Is there any plugin or any other way to do this?
I checked out this plugin https://marketplace.visualstudio.com/items?itemName=ryanstedman.tfs-pullrequest-dashboard&targetId=75aae682-e2e0-4f61-875b-c3b0544f2d4e&utm_source=vstsproduct&utm_medium=ExtHubManageList#overview but it only shows open pull requests for a particular project.
There isn’t the built-in feature or extension can see all open pull requests directly, also, I don’t find the third-party extension can do it.
I recommend that you can build the app or extension through Pull Request REST API, you can refer to that extension’s source code to do it with an extension.
This is now possible by visiting https://dev.azure.com/YOURACCOUNTNAME/_pulls
Is it possible to add members in bluemix track&plan with read-only access?
I want to limit the number of people who can add/modify work items into my project.
I understand your question that you want a more fine-grained access control for project members.
Can you not allow project members to edit work items? A short answer is no.
Check official website: https://hub.jazz.net/docs/projectadmin/
Project members have the fewest privileges and responsibilities. They can do these tasks:
- Add and edit work items
- Create Git branches for Git projects
- Create tags for Git projects
- Push and pull source code from the repository
- View and edit pipelines
- Add, edit, delete, and run pipeline stages or jobs
I think project members should have the access right to edit work items.
Bluemix track&plan is based on RTC(Rational Team Concert). I've been using RTC for team's project development for several years. It can be disturbing when someone removes a tag used in a query or changes work item to an incorrect status.
But the essence of track&plan is for team collaboration. Work item is critical to provide transparency and real-time status. Everybody on the team should have the right to add comments to the work item. My best practice is to use daily scrum meeting to review team dashboard and validate the work item status.
In real life, I seldom see team members deliberately update work items that don't belong to them. Instead, scrum master needs to motivate team to provide more update to the work items.
If you want to share the status to a stakeholder who's not in the project team, one doable option is to set your project as "public".
Try to access the link I created: https://hub.jazz.net/ccm51/quickplanner/jazzhub.html#items:projectId=_9b859SQ7EeesKZSRjqyxIQ&serverId=hub.jazz.net&planType=allwork&allIterations=true
Steps to set up your project as public:
1. Navigate to the Track&Plan dashboard. Click "Settings" icon
2. De-select "private" project checkbox & save