Sprints are "linked" across projects -- how to unlink?

[Mirko Raner]

I am aware of this question, but, frankly, other than emphasizing and re-emphasizing that "Sprints belong to boards not projects" and "Issues do not belong to boards", the given answers provide little practical advice as to how the problem can be fixed. (Also, I'm not 100% that my issue is really the same.)

So, here goes my problem: we originally only had one project, SP, but then later added two more projects, FE and HF. Each project is supposed to be on it's own sprint cycle. On the "Projects" page I see all three projects, each with their own board. When we originally split out the new projects from the original SP project, everything went well for the HF project, but the FE project and the SP project are still somehow linked. Specifically, it appears that both projects share the same sprint objects. This manifests itself in the fact that starting an SP sprint will also start the FE sprint (and vice versa). Also, when I change the name of the FE sprint, it will also change the name of the SP sprint, and vice versa. So, for all intents and purposes, it appears that the FE sprint and the SP sprint are really one and the same object (though they do show the correct issues in their respective boards). This linkage appears to be retained for all future sprints as well. As I stated earlier, each project has its own board, so I'm not sure what else to check.

How can I separate the SP and FE sprints from each other?

[Alexey_Rjeutski__Polontech_]

JIRA is the product that is required by jira agile, as jira agile is just a plugin. As for jira agile - it extends the functionality of jira in branches:

1. Scrum boards and scrum management

2. Kanban boadrs and kanban management

3. Different reporting that is related to agile methodology

4. Different gadgets to the dashboard that are related to agile methodology.

so jira agile + jira has all jira features + jira agile features. You cannot use jira agile without jira.

[Mudassar Pasha]

Thanks for summing that up. I am a little uncomfortable when my clients have to spend twice i.e JIRA liscenses + JIRA Agile liscences. Hence the tendency for a more detailed research.

But I guess it makes sense for Atlassian to have a core on top of which people can build their own platform with addons like Confluence, Bitbucket etc.