CODEWITHSUNDEEP
azure-devopsworkitem
Alexander S.
Alexander S.

Reputation: 844

Azure DevOps - New work item rule with action on "Iteration" field

I am trying to define new work item rule, and set action for field "Iteration", but it is not available. What is the problem, and how I can solve it?

enter image description here

Upvotes: 0

Views: 3575

Answers (2)

Leo Liu
Leo Liu

Reputation: 76760

Azure DevOps - New work item rule with action on “Iteration” field

That because Area Path and iteration path fields are not included in the custom rule field list. And this issue has been reported as feature request to the azure devops team:

Can't reference Iteration Path field when creating work item rules

After a period of investigation, I may have found the reason for this situation.

To found the reason why only Area Path and iteration path fields are not included in the custom rule field list, I suppose is that its type may be different from other fields.

So, I imported one Process from TFS, then I found that the type of Area Path and iteration path fields are TreePath:

enter image description here

We could not simply determine if a value is a TreePath like the string type. Since we may include \ in the Area Path and iteration path as string. For example, I create a new area name is MyTest\Bug, then my area path will change to: MyTestProject\MyTest\Bug. Now, problem is that \ between MyTest and Bug will treat as tree path instead of a string:

MyTestProject
     -----MyTest
            ----Bug

So, this may be the cause of this issue.

But I could not find any workaround for this issue, you could add your request for this feature 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.

enter image description here

Upvotes: 1

Shamrai Aleksander
Shamrai Aleksander

Reputation: 16018

I think, you do not have any problem. This is feature of azure devops: Iteration Path always contains some value (minimum: Team Project Name as root of iterations). So your rule will not work.

You may post your needs as feature request to the azure devops team: https://developercommunity.visualstudio.com/spaces/21/visual-studio-team-services.html?type=idea

That`s can be like: Add the Iteration Path field (and ignore root) or the Iteration ID field to the work items rules. Additionally describe your case and problem.

Upvotes: 0

Related Questions