Share via

Cannot create a feature in team

Anshu Garg 0 Reputation points
2026-02-03T14:07:31.9666667+00:00

In the ADO project, I have admin rights. Within the project, 2 teams have been created for me to manage the backlog. Both the teams are configured the same way.

Selecting the backlog option in one team, allows me to select all 4 options (being Intiative, Epic, Feature and User Story) from the drop-down (on the right top). And the "New Work Item" button right above it always enabled. The backlog updates based on the selection.

Surprisingly, selecting the backlog option in the second team does not have the same behavior. It allows me select all 4 options, but on selecting Feature, the backlog becomes empty and the "New Work Item" button right above it gets disabled. The other 3 options work the same as with the first team.

Regards

Azure DevOps
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Siddhesh Desai 3,275 Reputation points Microsoft External Staff Moderator
    2026-02-03T20:51:57.1866667+00:00

    Hi @Anshu Garg

    Thank you for reaching out to Microsoft Q&A.

    The behavior you are experiencing is due to team-level backlog configuration in Azure DevOps, not project-level permissions. Even though you have admin rights and both teams appear to be configured the same, Azure DevOps treats each team’s backlog as an independent, filtered view. When you switch backlog levels (Initiative, Epic, Feature, User Story), Azure DevOps applies the team’s Area Path, Iteration Path, and enabled backlog levels. In the second team, when you select Feature, Azure DevOps is unable to associate the Feature work item type with that team’s configuration. As a result, the backlog appears empty and the “New Work Item” button becomes disabled. This typically happens when the Feature backlog level is not fully enabled for the team, the team’s Area Path does not include any Feature items, or the Feature work item type is disabled or misconfigured at the process level. This is expected product behavior and has been observed in multiple Azure DevOps scenarios.

    Refer below points to resolve this issue or this is the workaround:

    Verify Feature backlog level is enabled for the team Go to Boards → Backlogs → Team Settings (gear icon) → Backlog levels and ensure that Feature is checked and saved for the affected team. Backlog levels are configured per team, and if Feature is not enabled, the backlog will be empty and item creation will be disabled.

    Check the team Area Path configuration (most common cause) Navigate to Project Settings → Teams → [Affected Team] → Areas. Ensure the correct Area Path is selected and that “Include sub-areas” is enabled. If Feature work items exist under a different area or sub-area not assigned to the team, they will not appear in the backlog.

    Confirm Feature work item type is enabled in the Process Go to Organization Settings → Process → [Your Process] → Backlog levels and verify that the Feature work item type is enabled and mapped correctly. If Feature is disabled at the process level, Azure DevOps will disable the “New Work Item” option for that backlog level.

    Validate Iteration Paths are assigned to the team Open Team Settings → Iterations and confirm that at least one iteration is assigned to the team. Missing or inactive iterations can also prevent backlog population and work item creation.

    0 comments
  2. Q&A Assist
    2026-02-03T14:07:46.3066667+00:00
    AI generated content. This question contains an answer created with AI from Q&A Assist. Learn more

    It seems that the issue you are experiencing with the second team's backlog may be related to the configuration of area paths or iteration paths for that specific team. Here are a few things you can check:

    1. Area Paths: Ensure that the area paths for the second team are correctly set up. If the area paths do not include the features you are trying to create, the backlog will appear empty when you select "Feature".
    2. Iteration Paths: Verify that the iteration paths are active for the second team. If there are no active iterations, it may prevent the creation of new features.
    3. Permissions: Even though you have admin rights, double-check that the team settings allow for the creation of features. Sometimes, specific configurations or permissions may limit what can be created.
    4. Team Settings: Compare the team settings between the two teams. There might be subtle differences in how the backlogs are configured that could affect functionality.

    If after checking these configurations the issue persists, you may want to consult the Azure DevOps documentation on managing team backlogs and settings to ensure everything is set up correctly.

    References:

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.