The general rules of structuring tasks is that the order of the structure builders is important and determines the resulting structure.
When conflicting structure builders are enabled, your tasks will be nested under only one of the builders:
Project and Sprint
Sprints are can be only created on Jira software boards which use a JQL filter.
Sprints are not related to any particular Jira project or in other words can be cross projects.
Automated task structure in this case will generate two separate branches.
Component and Versions
Components are subsections of project used to group data while versions control the scope of the release.
Components and versions used together will create separate branches in the task structure.
Depending on the order of the structure builders, an issue once nested under one of them will not move
Backlog and Project
Project has priority over the Agile Backlog synchroniser.
Which means that issues will be grouped under the project tasks rather than Backlog.
|Version and Sprints||As it is not possible to set a version of a Sprints in Jira it is also not possible to create such a structure.|
|Components and Sprints||Components are subsections of project and creating structure with Sprints just like in the case of versions would create two separate branches.|