CreateWorkItem chooses the wrong iteration year

[ViolettaCogoni]

• Extension: CreateWorkItem
• Environment: Azure DevOps Services (cloud)

I am using Create WorkItem so to create a Work Item at the end of the creation of a release. What I am trying to achieve is to add the current iteration. I followed the instructions by selecting "Current Iteration of the Team" and the YAML correctly displays

iterationPath: 'ApplicationTeamName@currentIteration'

as I expected, ApplicationTeamName being the specific team.

Please note that ithe terations for this team cover the whole period July 2017-- December 2050 nevertheless, at the creation of the Work Item, the wrong iteration is chosen. Let's say instead of 20th--24th June 2022, it picks 18th -- 24th July 2017!

[ReneSchumacher]

Hi @ViolettaCogoni,

does the team you selected have all iterations assigned to it? Since there could be multiple teams in a project and each team might have its own iterations that may even overlap (e.g., team A has two-week iterations while team B has three-week iterations) it's not enough to define the iterations in Project settings, Boards, Project configuration. You also must assign the iterations to the teams in Project settings, Boards, Team configuration:

Your description of the issue sounds as if there is an iteration for the current date (i.e., 20th - 24th of June 2022) but the last iteration that was assigned to the team was the one from 18th - 24th of July 2017. Can you check that?

[ViolettaCogoni]

Oh I see! I was not aware of the difference between the Team and the Project iterations. I will try the suggested way, thanks a lot!

[ViolettaCogoni]

Unfortunately I still have the same problem. Here are the Team iterations: while the following are the Project iterations: [...]

where the iterations I created for the Team have been added to the Project list, too. I do not know whether the duplicates have some kind of responsibility, still the final effect is that the wrong iteration is used, as you can see from the following image:

[ReneSchumacher]

Hm, are that really the team iterations for the team you selected in the task? There might be multiple teams and each must be configured individually. If you're willing and allowed to share a bit more information, could you send the full screenshots of the iteration configuration for the project and the team as well as the task configuration to PSGerExtSupport@microsoft.com so I can review it?

[ViolettaCogoni]

Ok so the point is to select the Team from General so to modify Iterations and Area Paths for the specific team! I will try as soon as possible :)

[ViolettaCogoni]

I confirm that your solution produces the desired effect! Thanks a lot for your support!