-
Suggestion
-
Resolution: Unresolved
-
None
-
1
-
7
-
At the moment, Teams field value will be inherited from parent tasks to sub-tasks. Provide the ability to assign different teams to parent issues and associated sub-tasks.
- mentioned in
-
Page Failed to load
Pierre in the linked thread articulated the issue very well.
I am just trying to anticipate the workload per discipline so that I can know if a very specialized scrum team member is needed at 100%, or not at all for the next sprints.
_https://community.atlassian.com/t5/Jira-questions/Why-is-Team-field-in-sub-task-disabled/qaq-p/1870306_
Consider the case where a story has acceptance criteria which are front end user specific (for a web application) and there are changes in middleware or backend systems. Delivery of the story is dependent on subtasks that are undertaken by people who have specific skills, and their availability is shared across other stories and epics. Its not practical to break up the user acceptance criteria into separate stories for each of the skill areas required to deliver them.