Exporting work item definition fails in Azure Devops 2019
I get the following error when I try to export a work item witadmin in Azure DevOps 2019
witadmin exportwitd /collection:<URL to team project> /p:AutoRI /n:Bug /f:<PathToExportedxml>\exported1.xml
The feature is disabled. Contact your Azure DevOps Server administrator. Process Id: 6483e73b-0c68-416d-88d8-9aff672828c7, Project Id: ceec55cd-a350-499f-82e2-47245c379a05
I am the Administrators of the project and I have the necessary authority.
Can some one please let me know how I can enable the feature? There is no documentation around this problem.
My permission is shown in the image:
It's not about basic agile or customized, actually it's related to process model you are using.
As declared clearly in witAdmin command line reference:
With witadmin, you can modify XML definition files to support the On-premises XML process model. For an overview of process models and what is supported, see Customize your work tracking experience.
To customize inherited processes, you just need to do it in the web portal. It's no need and also not able to export work item by using witadmin command.
More details, please kindly review our official tutorial here.
Hope this is clearly.
- How TFS version tracker will track the .PBL files of PowerBuilder code, does it track events, functions of .PBL files?
- Sonarqube TFS task returning error (401) Unauthorized on one project but not others
- Why does it say "Project with that name already opened in the solution"?
- How to get project on the source control in visual studio
- Team Explorer Everywhere Command Line Client workflow map validation errors
- TFS - An item with the same key has already been added
- How to pull source codes from TFS for building images in openshift pipeline
- Visual Studio / Nuget puts files in the wrong place
- CodeLens not showing references
- TFS 2017 Git API - Get Tag By Name
- How to branch my Visual Studio Online (TFS) Solution?
- No test found. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again
- WorkItem Creation Transaction Rollback
- Opening Source Control Explorer in Visual Studio 2022
- Remove project from visual studio solution
- Folders created in visual studio solution under solution explorer not appearing in source control explorer
- How to force Visual Studio to use the TFS source control provider and not GIT provider
- Error 500 while creating Azure DevOps server connector in Microsoft teams
- Get Visual Studio to run a T4 Template on every build
- How to Retrieve the Triggering Pipeline's runName in a YAML Release Pipeline
- 401 - Unauthorized: Access is denied due to invalid credentials when Trying to access the TFS API by postamn
- How to get a branch name for a dedicated changeset number via PowerShell
- TFS build write message to summary
- Exception setting "CursorPosition": "The handle is invalid." when running pipeline task using PowerShell Core
- Azure DevOps. Can't trigger a pipeline in Repo A when a commit is done in repo B
- TFS and referenced DLLs
- How to Migrate TFVS project to Azure Git Repos from different Organization
- TFS source control - new files not automatically detected as pending changes
- Azure DevOps API Authentication
- How can we make a Work Item Creator automatically a Follower?