JQL - Issues not in project sprint

Question

Hi,

Looking for a query or some way for me to find these issues.

Project ABC and DEF

If issues ABC-1, ABC-2 are in a sprint that was created in project DEF, is there a way for me to find it?

I want to search across all sprints in Jira. Ideally I would not allow an issue to be part of a sprint not within the project, or a jql that will alert me if someone moves an issue to a sprint outside the project.

John Price_q5a7ni · Answer

(First off, I left out some info. The full set of permissions around sprint management includes Edit Issues/Schedule Issues/Manage Sprints.)

Ideally you want a full Jira Admin to create a small set of useful roles like:

Administrators

Sprint Managers

Developers

Viewers

Then, have a Jira Admin create a permission scheme that uses those roles. Sprint Managers might have Schedule Issues and Manage Sprints on top of what Developers (team members) have. Then you set the Sprint Managers role members like this:

Project ABC = you

Project DEF = whoever adds stuff to sprints and starts/stops them on that team.

The DEF person won't be able to add your issues to their sprints because they aren't in the role in ABC.

DL_XM · Answer

Thanks @John Price !

How would #2 work? I don't see options in the permissions that will only limit project users.

We currently have our permissions configured so only project admins can Manage Sprints, but all other users still can view other sprints and add them to the issue.

John Price_q5a7ni · Answer

I don't think there's a native way to do this using just JQL if what you want is:

* I own project ABC and its sprints
* Someone over in DEF has a board filter that includes ABC issues and keeps adding my stuff to their sprints!

You can do this:

project = ABC and sprint is not empty and sprint not in ("ABC sprint 1", "ABC sprint 2")

but that isn't too maintainable. Better options:

* If it's an isolated issue, go talk to the owners of DEF about your overall agile process.
* Use permission schemes and roles so that only members of an ABC "Sprint Management" role can put ABC issues in sprints. That will totally block people over in DEF from doing this in the first place.
* Use Automation for Jira in the ABC project to catch Field Value Changed for Sprint and do something (email, etc.).

#2 is the simplest way I think, but I'd do 1&2 together.