How could I add custom values? I need to add custom values under the Planning section in work item for environments. I have tried to look in organizational settings, but I cannot really find the place where i can add such things. I have tried to Google this, but could not really found any relevant information. Any ideas? If you need more info, just ask!
I believe those are stored in Project Settings->Boards->Project Configuration, then click "Areas" or "Iterations" beneath the word "Boards".
Related
I'm looking to migrate a project from one org to another in Azure DevOps. We've ended up with two or three orgs, and this project that I'm looking to move has all sorts of weird and wonderful work items created and custom fields added. What I'm looking to do is move the project and then see if I can persuade the powers that be that certain things can be dropped but I have an immediate need to move as-is so that reporting and other work isn't impacted.
I have tried to get this to work with the migration tools (and tried to follow the videos) but have hit a dead-end. I think there are two issues potentially. One being the ReflectedWorkItemId. It says that it's not found in User Stories but I'm not sure how to resolve this? Do I go into user stories and add a field called 'ReflectedWorkItemId' and populate it with the work item number and/or add the same field in the destination org process?
It also mentions in the info that it can't find one of the Work Item Types - Processes. There are a few other custom work item types that have been created too but I assume it's given up on the first one. Do I have to create all of the work item types and the custom fields for each work item type in the destination org? Or am I getting the wrong end of the stick with this?
To provide sync as well as migration it is important that the tools knows which items have already been migrated. This is the purpose of the ReflectedWorkItemId field.
The field is not required in either case, however... if you don't have
the field then the system cant be re-run as it will re-copy all
completed work items. If you add the field to the target then it will
only copy those items it cant find. If you add the field to the source
(yes it needs to be the same refname), and set UpdateSoureReflectedId
to true then you can also filter the source, using a query and limit
what you load.
The former prevents duplicates, and the latter allows you to filter
the data load...
This is mentioned in this document. Here is a similar issue you can refer to.
TF201077 that usually happens when the target Project does not have a work item of that name. You can refer to this issue on github for help.
Presently I am using Devops Azure (Cloud).
For Work items is there a way to add and modify workflow Reasons.
State and Reason change
I am looking to add some custom reasons in the work item for each State.
Is there a way to change these. From the help, its mentioned, "You can add and remove workflow States. However, you can't add or modify workflow Reasons.". Any pointers to do this.
I am looking to add some custom reasons in the work item for each State.
I am afraid there is no such way to add some custom reasons in the work item for each State.
Although we can use custom fields and custom rules, it can only achieve one state for one reason.
That because Azure devops not allowed to have multiple rules with the same action type using the same conditions:
And on the other hand, we also could not add a list as value of Picklist items:
So, I do not believe we could add some custom reasonS in the work item for each State at this moment.
You could add your request for adding a list as value of Picklist items on our UserVoice site (https://developercommunity.visualstudio.com/content/idea/post.html?space=21 ), which is our main forum for product suggestions. Thank you for helping us build a better Azure DevOps.
Hope this helps.
There is no any news here. As workaround, you can:
Add a new custom field with a pick list with reasons and mark it as required. Add a picklist.
Use rules to set default values into your new field for each state transitions. Add a rule to a work item type.
I would like to add some custom fields to a Azure DevOps Project.
By default, there are only two fields available: Name and Description.
However, I would like to add additional information to the project like internal ProjectNo, OrderNo, OfferNo, Offer Date and so on.
Is there a way to do this?
As far as I'm aware there isn't any way to custom this aspect currently. You could always add it as a suggestion here; https://developercommunity.visualstudio.com/spaces/21/index.html.
Alternatively, depending on what you are looking to accomplish and how you want to use these new fields, could you make these 'projects' Epics (or create another Work Item type) under a 'global project'? If so you can easily customise work items to include these fields.
We have created a few extensions for Azure DevOps (0) that are pipeline extensions.
We are trying to create new extensions that can react to changes in work items of Azure Boards. The API's for interacting with changes in work items are fairly straight-forward, but we are struggling with configuration of the extension.
Essentially we need to allow the users to configure the extension on two levels
1) On "Organization level"
It should be possible for a user (Project Administrator) to configure parameters as "external system URL" etc. An example of this could be something like below mockup:
2) On "Project level"
For each project in Azure DevOps an admin should be able to configure parameters like "Enable/disable extension" or "External UID" etc. An example of this could be something like below mockup:
When the extension reacts to "Work item saved" it will query the parameters on both levels to figure out what to do.
My problem is: where the heck do I save this information? I could add a number of "custom fields" to the template in use, but since fields can only be added to work item types, it is really not ideal in any way.
Where can I save this information through the API's?
PS: Source code for our extensions are available as OSS (Apache license) here:
(0) https://bitbucket.org/projectum/
Thank you :-)
It turns out that Azure DevOps has a way to store data for extensions. It can store data on both Project Collection scope as well as User scope.
I think I will be able to use this to store the data I need. All I need now is to figure out where to put the UI that the user or admin will use to maintain this data.
https://learn.microsoft.com/en-us/azure/devops/extend/develop/data-storage?view=vsts
:-)
For #1, it somewhat looks like what you can configure under a pipeline's service connections. This is per project though and not at an organization level.
This might be easier to manage outside of an extension and instead just use a service hook to call some middle tier that accomplishes what you want.
I work in IBM RTC (Rational Team Concert); the Project Area I own is built on the IBM Formal Project Management Process Template.
I’m looking for a mean to get work items created programmatically;
I do want when I create a Change Request work item, to allow the selection of different teams and from this attribute(s), create automatically children work items Task directly assigned to the right team/member.
How would you recommend to do so?
Although it is not a direct answer to your issue, but I guess it would help. It's more like a workaround more than a solution to your requirement.
The work around is divided into two steps:
Create a work item template from a CR with all its sub tasks included in the work item template.
Create a CR using the previously created template programmatically.
Note: This means that you'll need to create a work item template for each team.