In a Program project, there is a special Tracker Workflow post-action "Add to top backlog" that allows users to set up a workflow so that changing the status of a Feature artifact moves it automatically in the Program Top backlog. As of today, this post-action is set up to only appear (be visible) and only run when the Program is linked to at least one Team project.

This makes it hard to use Templates, because by nature, a Template of a Program will never be linked to any Teams, as its purpose is to be duplicated. When this duplication occurs, the code checks again to see if there are any Teams linked to the template, and as a result, the workflow cannot be inherited.

As discussed with Product Owner, there is no real functional reason to forbid this post action when the Program has no Teams. At worst case, it will add to the top backlog, but then it cannot be planned anywhere because there are no Teams.

The plan to fix this issue is the following:

1. Introduce a new check to verify that a project is a program. This check verifies that the "Program" service is enabled and that the current user can access the project. It does not verify the presence of Teams whatsoever.
2. Replace the existing check with the new check at 1 when listing the workflow post-actions.
3. Replace the existing check with the new check at 1 when running the workflow "Add to top backlog" post-action.
4. As a result, the project inheritance should be fixed. The workflow post-action should be inherited.